Perimeters
  • ✨Getting Started
    • Overview
    • Quick Start
      • First Login
      • Connecting things up
        • Prioritize IdP Integration
        • Integrating Response & Automation Applications
        • Following Compliances
      • Extend your Coverage
        • Integrate Additional SaaS Services
        • Integrate Supported Shadow Applications
        • Close Some Issues
      • First Use
    • Making the most of Perimeters
  • 🚪Perimeters Portal
    • Dashboard
      • Use Cases
    • Inventory
      • Applications
      • Users
      • Shadow Applications
    • Rules
      • Use Case Issues
    • Threats
      • Rules
      • Event Activity
    • Compliance
      • Single Framework
    • Settings
      • Domain Management
      • Identity Management
      • Reports
      • Action Templates
      • Application Logs
    • Account Settings
  • 🪢Connecting Perimeters
    • General Instructions
    • SaaS Applications
      • Atlassian Guard (Previously Access)
      • Bitbucket
      • BambooHR
      • Cisco Duo
      • Confluence
      • Custom Integration
      • Datadog
      • DocuSign
      • Dropbox
      • EntraID
      • GitHub
      • Gitlab
      • Google Workspace (G Suite)
      • Hubspot
      • Intune
      • Jira Software
      • Microsoft 365
      • Monday
      • MongoDB (Atlas Mongo)
      • Okta
      • OneLogin
      • OpenAI
      • Salesforce
      • Sentry
      • ServiceNow
      • SharePoint
      • Slack
      • Teams
      • Trello
      • Zendesk
      • Zoom
    • Response & Automation
      • custom Email
      • eMail
      • Jira Software
      • Slack
      • Webhook
      • Splunk
      • Zendesk
  • Release Notes
    • June 2024
  • Additional
    • Glossary
    • FAQ
    • Support
Powered by GitBook
On this page
  1. Connecting Perimeters
  2. SaaS Applications

Custom Integration

This guide will walk you through the process of creating a custom integration. Follow each step carefully to ensure a successful integration.

Step 1: Display Details

  • Select LogoYou have two options to select a logo:

    • Choose Avatar Color

      Select a color for your integration avatar

    • Upload Avatar Image

      Upload a custom image (maximum size: 5KB)

  • Enter Integration DetailsProvide the following information:

    • Integration Name

      The name of the SaaS service to which data belongs

    • Display Name

      An alias you can give to the integration

Step 2: Data Source Details

  • Upload Data FileRequirements for data file:

    • File Size

      Maximum file size: 50MB

    • Supported Formats

      CSV and JSON files are supported

    • Template Files

      Download template files to check the expected data format

      CSVJSON

Step 3: Data Validation

  • Monitor Data Validation: You can monitor the data validation results to ensure your data is synced correctly or find the issues.

    • Fix Validation Issues

      If validation fails, you'll need to correct the data format and try again.

    • Complete Integration

      Once validation is successful, you can complete the integration process.

Data Format Guide

This guide provides detailed information about the required data format for your integration. Please ensure your data follows these specifications exactly.

Required Fields

The following field is mandatory and must be included in your data:

  • emailId

    User's email address (must be a valid email format)

Optional Fields

The following fields are optional and can be included if available:

  • firstName

    User's first name (string)

  • lastName

    User's last name (string)

  • role

    User's role (must be one of:)

    SUPERADMINADMINUSER

  • createdOn

    Date of creation (format: DDMMYYYY, e.g., 01012024)

  • userStatus

    User's status (must be one of:)

    ACTIVEDISABLEDDELETED

  • accountType

    Account type (must be one of:)

    USERSERVICE

  • department

    User's department (string)

  • mfaEnrolmentStatus

    MFA enrollment status (true/false)

  • accountPaymentStatus

    Payment status (must be one of:)

    PAIDUNPAIDNA

Data Format Examples

Here are examples of valid data entries:

JSON Format

{
  "firstName": "John",
  "lastName": "Doe",
  "emailId": "john.doe@example.com",
  "department": "Engineering",
  "role": "ADMIN",
  "createdOn": "01012024",
  "mfaEnrolmentStatus": true,
  "userStatus": "ACTIVE",
  "accountPaymentStatus": "PAID",
  "accountType": "USER"
  }

CSV Format

firstName,lastName,emailId,department,role,createdOn,mfaEnrolmentStatus,userStatus,accountPaymentStatus,accountType
  John,Doe,john.doe@example.com,Engineering,ADMIN,01012024,true,ACTIVE,PAID,USER

Important Notes

  • Data Validation

    All required fields must be present and valid for successful integration

  • Date Format

    The createdOn field must follow the DDMMYYYY format (e.g., 01012024 for January 1, 2024)

  • Enum Values

    Fields with enum values (role, userStatus, accountPaymentStatus, accountType) must use exact values as specified

PreviousConfluenceNextDatadog

Last updated 16 days ago

🪢