Skip to content

Integrations

This page covers common integration issues for Sources, Scout connectors, and API tokens.

I can’t create a Source

Symptoms

  • Validation fails when saving a new source.
  • The source saves, but doesn’t work.

Likely causes

  • Missing permissions in the service account.
  • Invalid credentials.
  • Network or allowlist constraints in your environment.

How to fix

  • Use a dedicated service account with least privilege.
  • Re-check credentials and required scopes.
  • Try connecting with the minimum configuration first.
  • If your environment requires allowlisting, contact Support to confirm what endpoints must be reachable.

Related: Sources

Scout connector is disconnected or keeps expiring

Symptoms

  • A connector shows as disconnected, or Scout can’t access content you expect.

Likely causes

  • Your external session expired or was revoked.
  • Permissions changed in the external system.

How to fix

  • Re-authorize the connector in Settings → Connectors.
  • Confirm you can access the target content directly in the external system with the same account.

Related: Scout Connectors

My API token stopped working

Symptoms

  • API calls fail with authentication errors.
  • Modulos Client reports an authorization failure.

Likely causes

  • The token expired.
  • The token was revoked.
  • The token is not being passed correctly.

How to fix

  • Create a new token in Settings → API Tokens and rotate it in your integration.
  • Verify the token is stored as a secret and injected at runtime, not hard-coded.

Related: API Tokens, Modulos Client

When to contact Support

For integration issues, include:

  • integration type, for example Datadog or GitHub
  • whether it affects one user or the whole project
  • any recent credential rotation or permission changes
  • the timestamp and a screenshot of the error where possible