Connect tools, scripts and AI assistants
Choose an integration route, scope access and verify actions correctly.
Integrations lets authorized tools work with Social. Available options can include an API, compatible AI-assistant tools, a command-line interface and no-code HTTP workflows. Use the setup instructions shown in your current DigLab Social workspace for exact endpoints and configuration.
Choose and authorize a route
-
Open Integrations and choose the card matching your tool or workflow.
-
Identify the action you need: read analytics, create drafts, upload media, schedule posts or handle another supported operation.
-
If an API key is required, choose New API key, give it a purpose-specific name and select only the needed scopes.
-
Restrict access to the intended workspace where supported.
-
Copy the key into the destination tool's protected credential field or secret store. Do not put it in source code, screenshots or shared chat messages.
Test a harmless operation
Follow the current setup instructions to make a read-only request, such as listing the intended workspace's accounts. Confirm the account and workspace identifiers before enabling actions that write or publish. For a no-code workflow, begin with a draft action and a small test input. Inspect the resulting draft inside Social. Add explicit mapping for account, caption, media and schedule rather than relying on whichever workspace was used most recently.
Publishing through an integration
Creating a draft never publishes it. A planned date attached to a draft is only a planning field. Scheduling and publication require the corresponding action, and member approval rules still apply where enabled. An accepted request can run asynchronously. Store its identifier, check the final status and verify the provider post ID or link. On uncertain or partial failures, check the existing job and destination before retrying.
Maintain and revoke access
For rotation, create a replacement credential, update the integration, test it and then revoke the old key. Review last-used information where available. Revoking a key can break every workflow using it, so identify those workflows first. For errors, distinguish invalid credentials, missing scopes, wrong workspace, validation errors and exhausted limits. Share error codes and request identifiers with support while removing credentials.
Connect through the current DigLab setup
Open the integration card in your current DigLab Social workspace and use the endpoint and authentication method shown there. OAuth-based assistant connections and API-key workflows are distinct: do not paste a key into an OAuth sign-in field or copy a URL from an unrelated deployment.
For MCP, use MCP DigLab documentation alongside the Social setup card. Start with a read-only request:
List the Social workspaces I can access. Identify the intended workspace, then list its connected publishing accounts. Make no changes.Inspect the actual tools exposed to that connection. Tool availability can differ by deployment and account. A successful read verifies that read path only; it does not prove media upload, draft creation, scheduling, approval or publication.
Track a write through its final result
- Resolve the intended workspace and account identifiers from current discovery.
- Prepare a small authorized draft and inspect it in Social before automating broader writes.
- For asynchronous operations, keep the returned job or post identifier and check final state.
- Verify every destination independently. After a timeout or partial result, read existing state before retrying.
Keep keys and signed upload URLs out of screenshots, shared prompts and logs. For HTTP errors, separate authentication failures, insufficient access, invalid inputs and rate limits; provide support with a redacted error and request identifier.