Early access. These guides cover the current product build. Access and connected-channel availability depend on your organization's setup. Public Instagram messaging access is not available yet.
Connect a channel
Channel connection is available only in eligible early-access workspaces. If your workspace says setup is unavailable, the connection controls are not enabled yet. These instructions do not mean Meta has approved every account or capability.
Choose an account
- Sign in as a workspace owner or admin and open Channels.
- Choose Connect Instagram or Connect Facebook. Complete the provider's login and permission steps.
- Choose the account you want to use. An account connected to another workspace cannot be selected.
- Return to Channels and check its status and permissions. Completing login alone does not mean every Runner can perform every action.
The current Instagram connection uses a professional account linked to a Facebook Page. If setup expires, start again from Channels. A failed or cancelled attempt shows a short message there; it does not show access credentials.
Reconnect when access needs attention
Use Reconnect next to the account and complete login again. Reconnecting is the way to renew access; a background check does not renew it for you. If the button is unavailable, check that you are an owner or admin and that channel setup is enabled for your workspace.
An expired or rejected grant needs renewed access. A temporary provider outage alone does not change the account to that state. If the recorded expiry passes while a check is running, the account still needs renewed access, even if the provider could not respond. Missing permissions can still prevent an action even when the connection is present.
If Reconnect alerts is available in Settings, a workspace owner can opt in for notices about Facebook or Instagram channels that need reconnection. This uses that owner's verified sign-in email, is separate from Watch daily briefings, and can include a channel that already needs attention. The setting is off by default and may be unavailable for your workspace. A notice does not reconnect the channel; check Channels for its current status. Each channel and access version can generate at most one notice for that owner, so opting in again does not resend a notice already recorded for the same access version. An email provider's acceptance does not confirm delivery.
Removing access and deleting data
Revoking SetToRun's access at the provider and deleting data already stored in SetToRun are separate actions. Revoking access does not itself delete your workspace, contacts, activity history or stored media. Automatic data deletion is not implemented by the connection or revocation flow.
Automatic handling of provider revocations is off by default and is not enabled for this release. Where enabled, a verified revocation can remove the stored access credential for a matching connection and mark it as needing renewed access. A request already sent to the provider cannot be recalled by a later revocation.
Older connections may not have the verified connection information needed for automatic matching. Do not treat an unchanged channel status as proof that access still works. Check Channels and use Reconnect if you want to grant access again. Reconnecting grants access again; it is not a request to delete previously stored data.
Read connection activity
In the night log, Channel setup describes connection steps. Where background checks are enabled, Channel maintenance describes access checks. Both are separate from Runner work and excluded from Runner totals.
A check that confirms access says the stored token was accepted at that time. It does not prove all permissions, linked-account settings, webhook delivery or future availability. Background checks are off by default and must be enabled for the workspace. Read the recorded result and the current channel status; finishing a check does not always mean access is still valid.
Once your channel is ready, test a Play with a sample before relying on live activity.