Skip to content

Integrations

Integrations let you save authentication credentials for external systems and reuse them across campaigns. Instead of entering credentials each time you configure an Outbound API block, you set them up once here and select them from a dropdown.

Managing the Integrations

Go to Segmentation → Integrations in the left navigation to manage the list of Integrations.

image.png

Adding an Authentication

  1. Click Add integration.
  2. Enter a name and description.
  3. Select a client authentication method (see Authentication methods available for more details) :
    • OAuth 2.0
    • HTTP Basic
  4. Fill in the required fields.
  5. Click Test connection to verify the credentials work before saving.
  6. Click Save.

image.png

Authentication methods available

If you are unsure about the authentication method and credentials, contact your IT team or the team managing the external system (e.g. your CRM or CDP provider).

HTTP Basic

Use HTTP Basic when the external system requires basic username/password authentication. - Username: The username provided by the external system.
- Password: The password associated with that username.

OAuth 2.0 method

Use OAuth 2.0 when the external system requires token-based authentication. - Client ID: The client identifier provided by the external system.
- Client Secret: The secret used to authenticate your client.
- Token endpoint: The URL used to obtain an access token.
- Additional headers (optional): Any extra headers required by the external system when requesting the token.

Nexus stores these credentials securely and obtains access tokens automatically when the Outbound API block sends a request using this Integration.

Editing an Authentication

Click on an existing Authentication in the list to open and edit it.

Changes take effect immediately for all Outbound API blocks using that Authentication.

Deleting an Authentication

Select an Authentication from the list and click Delete.

Deleting an Authentication does not affect past campaign runs. It will cause future runs of any block that uses it to fail — remove it only when it is no longer in use.

Using an Authentication in a campaign

Once saved, Authentications appear in the Authentication dropdown when configuring an Outbound API block. See Outbound API block for details.