Connect social accounts

Social (product name Social Engagement) is GATE's tool for social content and outreach. Unlike the read-only integrations, it drives its own browser-based account sessions, AI image/video generation, posting, and outreach campaigns that run on their own once you launch them. This walkthrough takes you from nothing to a live campaign.

Unlike the read-only Instagram and Facebook proxies (which only report your own owned-account stats), Social actually posts and runs outreach. See Social integrations for the distinction and the integrations matrix for the full surface.

Which platforms work

Instagram and LinkedIn are fully supported. Facebook is content/posting only — no profile read, no lead screening, no outreach, and no AI "Set up from my account". Do not promise Facebook outreach.

Prerequisites

• Your bot has been granted Social access. If a target account revokes that access, calls return a 403 and a human master must re-authorize it.
• If your bot serves multiple orgs (or is a master bot), it identifies which org it's acting for on every request — nothing you need to specify yourself.
• For sign-in challenges, a human who can solve a 2FA/CAPTCHA prompt live in a browser.

Step 1 — Add a Brand

A Brand (profile) holds the shared brand voice, hashtags, signature line, and pacing for every account under it. One Brand can carry accounts on more than one platform.

Tell your bot the brand name along with its voice and primary language — for example: "Set up a new brand called Acme Studio, warm and concise voice, primary language English." Your bot creates the profile from that.

Step 2 — Connect and sign in the account

Tell your bot which brand, platform, and account handle to connect, then have it sign the account in — sign-in opens a real browser session. For example: "Add my Instagram account @acmestudio to the Acme Studio brand and sign it in." You'll need to give the bot the account's password to complete sign-in.

If the platform throws a 2FA or CAPTCHA challenge, the bot will tell you it needs a human to solve it live and share a link to the visible browser session. Open that link, solve the challenge yourself, then tell the bot to confirm the sign-in.

Step 3 — Set up from my account

"Set up from my account" reads the connected Instagram/LinkedIn account and drafts the brand fields (voice, ideal lead, signature line, default hashtags, language). This AI step is dashboard-only — run it from the Brands page in the dashboard.

Your bot can't trigger it for you.

(A bot can still write those fields directly if you ask it to update the brand's profile.)

Step 4 — Create a campaign

Outreach discovers leads, AI-screens them against your brand's ideal lead, then acts — one action per person, paced across ticks. Tell your bot what to target and which actions to take — for example: "Start an outreach campaign on my Instagram account targeting indie coffee roasters, with likes, comments, follows, and DMs."

Once a campaign is active, GATE runs it autonomously, one paced action per tick. The bot creates and steers campaigns; it does not loop firing actions. You can also ask the bot to make the campaign recurring (keep engaging new leads each pass), create it without firing right away, or supply your own DM/comment templates so it sends your text verbatim with placeholders filled in.

Step 5 — Understand the safety limits before you run

Automation runs under a set of built-in safety limits. Know these before launching:

• Per-action caps — 8 action buckets, each a 24h-rolling day cap plus an hour cap, set by a safety preset (0 Brand New … 4 Established). Ask your bot to check an account's caps if you want to see the current limits.
• Per-user cooldown — a cross-action gate (default ~36h) so one handle isn't liked, commented, followed, and DMed in quick succession.
• Burst detection & pacing — randomized gaps within active hours; a burst guard pauses if activity spikes.
• Security scanner — a post-action page scan (off | warn | halt); halt can lock the account.

If a campaign stops, distinguish stopped (operator stopped it on purpose) from failed (crashed or reaped by the watchdog), and check paused_reason (NULL = operator pause, proxy_credit_exhausted = auto-pause that resumes on credits). Start a fresh account on a low preset.

Going deeper

See Social integrations for capabilities and the read-only proxies, and the integrations matrix for the full command surface.