IntegrationsOverviewManaging connections

Managing connections

Console → Connectors, connected list with one connection's menu open

Console → Connectors, connected list with one connection's menu open

screenshot slot, save as public/screens/…png and set  src

Pause and disconnect are different operations with different consequences. The menu keeps them apart on purpose.

Pause versus disconnect

Pause (enabled: false)Disconnect
New eventsStopStop
Existing eventsKeptKept
Decisions drawn from themKeptKept
The grant at the providerKeptRevoked
Re-enablingOne clickFull consent flow again

Pause when you are debugging noise. Disconnect when the relationship with that tool is over.

When the person who connected it leaves

The grant belongs to whoever consented. If that account is deactivated at the provider, the connection stops working, usually quietly, with events simply ceasing.

Two mitigations, in order of preference:

  1. Connect with a service account your organization owns, not a person's account, for anything long-lived.
  2. Watch for silence. A source that stops producing events is the symptom.

Diagnosing a quiet connection

Work down this list:

  1. 1

    Is a trigger subscribed?

    A connection with no trigger produces nothing at all.

  2. 2

    Is the connection enabled?

    A paused connection looks identical to a broken one from Activity.

  3. 3

    Is the permalink base URL set?

    Slack and Jira events are rejected without one. Nothing arrives, and the cause is not in the connector.

  4. 4

    Is anything failing to deliver?

    Connectors → the connection → Failed deliveries lists every delivery that arrived and then failed downstream. Nothing is dropped silently, so an empty list here means the problem is upstream of Memnox.

  5. 5

    Has the grant expired at the provider?

    Reconnect. The provider owns refresh, so an expired grant is fixed there.

Pulling events by hand

For a one-off pull outside the trigger flow, open Connectors → the connection → Sync now and choose a window.

Useful when re-testing after a configuration change or filling one specific gap. For a whole history, use backfill instead: it pages, respects the provider's rate limits, and reports progress.

Connection limits

connectedSources is a plan limit. Disconnecting frees a slot immediately; pausing does not.