POST /accounts/{account_id}/one/integrations

Creates a new integration for the specified application. Integration creation with OAuth is not supported by API at the moment. For other auth methods, use GET /v2/applications/{application_id}/credential-guide to see the required credential structure and example payloads for each vendor.

Servers

Path parameters

Name Type Required Description
account_id String Yes

Cloudflare account identifier.

Request headers

Name Type Required Description
Content-Type String Yes The media type of the request body.

Default value: "application/json"

Request body fields

Name Type Required Description
use_cases[] Array No

List of use case or feature slugs to enroll (e.g., ['casb', 'ces', 'auto_remediation']).

application String Yes

Vendor/application slug (e.g., GOOGLE_WORKSPACE).

  • BITBUCKET - BITBUCKET
  • BOX - BOX
  • CONFLUENCE - CONFLUENCE
  • DROPBOX - DROPBOX
  • GITHUB - GITHUB
  • GOOGLE_WORKSPACE - GOOGLE_WORKSPACE
  • JIRA - JIRA
  • MICROSOFT_INTERNAL - MICROSOFT_INTERNAL
  • SALESFORCE - SALESFORCE
  • SLACK - SLACK

Valid values:

  • "MICROSOFT_INTERNAL"
  • "BITBUCKET"
  • "DROPBOX"
  • "BOX"
  • "CONFLUENCE"
  • "SLACK"
  • "GITHUB"
  • "JIRA"
  • "SALESFORCE"
  • "GOOGLE_WORKSPACE"
name String Yes

Name of the integration.

auth_method String No

Authentication method slug (uses default if omitted).

credentials Object Yes

Credentials for the integration.

permissions[] Array No

List of permission scopes (uses policy defaults if empty).

dlp_profiles[] Array No

List of DLP profile IDs to associate.

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.