Distribution
Integrations and connections
Add integrations, review credentials, and resolve connection failures.
For workspace users and administrators · Updated October 1, 2026
What this module is for
Add integrations, review credentials, and resolve connection failures.
Use this page when you need to complete the task yourself and understand what each action changes. The steps name the relevant screen, explain why the action belongs in the workflow, and state what to verify before moving on.
Before you start
- Sign in with a role that can view or change the records in this guide.
- Have the product, file, channel, or workspace information ready before starting an action that saves data.
- Use a small test record or file first when an action affects multiple products or a connected channel.
1. Connect a service
Complete these actions in order. They describe the screen to use, the decision to make, and the evidence to check before you move to the next stage.
-
Step 1.1
Do this: Open Integrations and select a provider or the available connection action.
Why this matters: This keeps the connect a service work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Look for a confirmation message, a newly created record, or a job status entry. If nothing changes, read the inline field error or job detail before retrying.
-
Step 1.2
Do this: Supply the credentials and mapping details requested by that provider.
Why this matters: This keeps the connect a service work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Confirm that the named screen or panel is visible and contains the expected values. If a control is missing, check your workspace role before continuing.
-
Step 1.3
Do this: Open the integration detail and review Connection Details and Credentials.
Why this matters: This keeps the connect a service work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Look for a confirmation message, a newly created record, or a job status entry. If nothing changes, read the inline field error or job detail before retrying.
2. Operate the connection
Complete these actions in order. They describe the screen to use, the decision to make, and the evidence to check before you move to the next stage.
-
Step 2.1
Do this: Refresh the integration status after setup or a configuration change.
Why this matters: This keeps the operate the connection work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Confirm that the named screen or panel is visible and contains the expected values. If a control is missing, check your workspace role before continuing.
-
Step 2.2
Do this: Review sync failures alongside channel and export jobs.
Why this matters: This keeps the operate the connection work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Confirm that the named screen or panel is visible and contains the expected values. If a control is missing, check your workspace role before continuing.
-
Step 2.3
Do this: Disconnect an integration from its list action only when downstream delivery has been moved or stopped.
Why this matters: This keeps the operate the connection work traceable and makes the next review, validation, or handoff easier to complete.
Check before continuing: Look for a confirmation message, a newly created record, or a job status entry. If nothing changes, read the inline field error or job detail before retrying.
Events and statuses to watch
Actions such as saving, importing, exporting, connecting, publishing, and approving can either update a record immediately or create background work. Wait for the on-screen confirmation and then check the relevant list, detail view, or job status before repeating an action.
- Saved or created: confirm the record appears with the intended values.
- Queued, running, or processing: wait for completion and open the job or event detail if progress stops.
- Failed, partial, rejected, or blocked: read the specific message, correct the source data or permissions, then retry only the affected work.