Signup comes with $1 in credit. No subscription needed.Claim your $1
Docs: Connected accounts
Guides

Connected accounts

Connect LinkedIn, Instagram, WhatsApp and Gmail accounts, send invitations, messages and LinkedIn comments, read replies, and manage connections, send limits and the monthly fee.

Connect your own LinkedIn, Instagram, WhatsApp or Gmail account to RouterGrowth, then let your agent send messages and read replies through it with the same RouterGrowth key, over REST, the CLI or MCP. Each connection belongs to your workspace. This page covers connecting accounts, what each channel can do, send limits, the monthly fee and the REST routes that manage accounts.

Gmail connects a mailbox you already own. To give your agent new inboxes on a domain you own, see email inboxes and sending.

Capabilities

Channel Accounts (free) Look up Send Read
LinkedIn linkedin.accounts, linkedin.account linkedin.search, linkedin.profile linkedin.invite, linkedin.message, linkedin.comment linkedin.messages, linkedin.invitations_sent (free)
Instagram instagram.accounts, instagram.account instagram.profile instagram.message instagram.messages
WhatsApp whatsapp.accounts, whatsapp.account whatsapp.profile whatsapp.message whatsapp.messages
Gmail gmail.accounts, gmail.account none gmail.send gmail.messages

.accounts lists the workspace's accounts on one network and refreshes their status; .account connects, reconnects or checks one. Use inspect for each capability's current schema and price. The examples run the CLI with a live key and wait up to 30 seconds for the result; their --max-cost caps leave headroom over the prices inspect gives.

Connect an account

Open Connected accounts in the dashboard, choose the network and give the account a name. The sign-in happens on Unipile's hosted page: the account's own sign-in for LinkedIn and Instagram (two-factor included), a QR or pairing code for WhatsApp, Google OAuth for Gmail, where the mailbox owner authorizes access. Passwords and OAuth tokens never reach RouterGrowth.

An agent can request the same hosted link. Run .accounts first, so you reuse an account that is already connected:

routergrowth run -c whatsapp.accounts -i '{}' --wait 30
routergrowth run -c whatsapp.account -i '{"name":"sales"}' --wait 30

A new connected account comes with a monthly plan (Starter and up), or with the trial connection. Without a plan, a workspace's first LinkedIn account and its first Gmail account each connect free for 7 days: no card, no seat charged. trial_until on the account says when the trial ends, and .account and .accounts repeat it in next_step with a link that starts a plan. If a plan starts before then, the account stays and its seat is charged from that day. If none does, the account is removed from the workspace and from the provider; your LinkedIn or Gmail account itself is untouched. A workspace gets one trial per network, and a login that had its trial in another workspace does not get a second one.

Past the trial, or on Instagram and WhatsApp, .account on pay per call answers plan_required (HTTP 402) with a start_plan link instead of a sign-in link, and the dashboard shows See plans. On the account listing, can_connect says whether a new account can be connected now and trial.available whether it would be a trial. Reconnecting an account the workspace already holds never needs a plan. The same login signed in twice in one workspace is kept once: the second sign-in is removed and charges nothing.

Open the returned connect_url (valid up to 24 hours), finish the sign-in, and run the same .account call again to confirm connected: true; the dashboard updates on its own. If the link expires, request another one with the same name. Without a name, .account reports the account already connected (with its reconnect link when its login dropped) instead of minting a link; only when the workspace has no account on that network does it mint one, named main.

status on each account is OK when connected, PENDING while nobody has used the link, EXPIRED when the link ran out, CONNECTING while the account syncs, and CREDENTIALS when the session dropped: run .account with the name and it returns a reconnect link in connect_url (the dashboard shows Reconnect on that row). Reconnect under the same name rather than connecting the account again under a new one. ERROR, STOPPED, PERMISSIONS and DISCONNECTED also mean the account cannot send; run .account with the name again. A dropped session also arrives as an account.disconnected event.

Pass account_id as the account's name or its returned ID. You may omit it only when exactly one account of that network is connected. A name is stored as a label of lowercase letters, digits and dashes, up to 24 characters. Each network has its own names: WhatsApp and Gmail can both have an account named sales, and their connections remain separate.

LinkedIn

routergrowth run -c linkedin.search -i '{"account_id":"alex","keywords":"head of growth fintech","location":["Lisbon"]}' --max-cost 0.01 --wait 30
routergrowth run -c linkedin.invitations_sent -i '{"account_id":"alex"}' --wait 30
routergrowth run -c linkedin.invite -i '{"account_id":"alex","profile_url":"https://www.linkedin.com/in/janedoe","message":"Saw your talk on pricing pages. Happy to connect."}' --max-cost 0.02 --wait 30
routergrowth run -c linkedin.messages -i '{"account_id":"alex","unread":true}' --max-cost 0.01 --wait 30
routergrowth run -c linkedin.message -i '{"account_id":"alex","chat_id":"CHAT_ID","text":"Thanks, Tuesday works."}' --max-cost 0.02 --wait 30
routergrowth run -c linkedin.comment -i '{"account_id":"alex","post_url":"https://www.linkedin.com/feed/update/urn:li:activity:7391234567890123456","text":"Clear breakdown, thanks for sharing the numbers."}' --max-cost 0.02 --wait 30
  • linkedin.search: classic search, or Sales Navigator with api: "sales_navigator", by keywords or a pasted search url, with location, company, industry and network_distance filters. Place, company and industry names resolve to LinkedIn ids; a name with no match is dropped and named in the result's note. Each person carries the provider_id and profile_url the next calls take.
  • linkedin.profile: one profile as your account sees it; connected: true (a first-degree connection) is how an accepted invitation shows.
  • linkedin.invite: a connection request with an optional message of up to 200 characters, 300 with Premium. A free account gets about 5 invitations with a note a month; after that, send without one. Someone already connected, already invited or not invitable again yet comes back as a free no_match.
  • linkedin.invitations_sent (free): the pending invitations, counted against today's and this week's caps. Run it before a batch.
  • linkedin.message: chat_id replies in a thread; profile_url or provider_id starts a conversation. An InMail takes a subject and either inmail: true (Premium credits) or api: "recruiter" or "sales_navigator" (that product's credits); linkedin.accounts with inmail_credits: true shows each balance. attachments sends up to 10 images or files with the message, 10 MB in all, each as a public https url fetched at send time or as inline data_base64 (4 MB in all), on a reply or a new conversation.
  • linkedin.messages: conversations, newest first; unread: true keeps the ones with new replies, chat_id reads one thread.
  • linkedin.comment: a comment on a post, named by post_url or by post_id (the activity id social.search returns, or the post's urn), up to 1,250 characters; with comment_id it replies in that comment's thread instead. The result names the post's author, ready for linkedin.invite. A deleted post, one the account cannot open or one with comments turned off is a free no_match. The comment is public under the account holder's name; social.comments with the post's link as url reads the replies.

Instagram

routergrowth run -c instagram.profile -i '{"account_id":"studio","handle":"@atelier.nord"}' --max-cost 0.01 --wait 30
routergrowth run -c instagram.message -i '{"account_id":"studio","handle":"@atelier.nord","text":"Loved the spring collection."}' --max-cost 0.02 --wait 30
routergrowth run -c instagram.messages -i '{"account_id":"studio","unread":true}' --max-cost 0.01 --wait 30
  • instagram.profile: one account by handle, profile_url or provider_id: bio, links, the business email and phone when the account shows them, whether it follows you, and the messaging_id a new conversation needs.
  • instagram.message: chat_id replies in a thread; handle, profile_url or messaging_id starts a conversation. Text only. A first message to someone who does not follow the account lands in their requests folder.
  • instagram.messages: conversations, unread: true or one thread by chat_id, as on LinkedIn.

There is no Instagram search or invitation: find accounts with social.search.

WhatsApp

Look up a recipient, send a message, then read conversations:

routergrowth run -c whatsapp.profile -i '{"account_id":"sales","phone":"+14155550123"}' --max-cost 0.01 --wait 30
routergrowth run -c whatsapp.message -i '{"account_id":"sales","phone":"+14155550123","text":"Here is the information you requested."}' --max-cost 0.02 --wait 30
routergrowth run -c whatsapp.messages -i '{"account_id":"sales","unread":true,"limit":20}' --max-cost 0.01 --wait 30
routergrowth run -c whatsapp.messages -i '{"account_id":"sales","chat_id":"CHAT_ID","limit":20}' --max-cost 0.01 --wait 30
routergrowth run -c whatsapp.message -i '{"account_id":"sales","chat_id":"CHAT_ID","text":"Thanks for confirming."}' --max-cost 0.02 --wait 30

Phone numbers must start with + and include a country code. Alternatively, use provider_id from a profile or conversation, and keep IDs ending in @s.whatsapp.net or @lid exactly as returned. Existing chats, including supported group conversations, can be read and replied to by chat_id, which must belong to the selected account; creating or managing groups is not exposed.

whatsapp.messages returns chats when no chat_id is supplied, and messages for a thread. Pass the returned cursor for another page. after accepts an ISO 8601 timestamp with a timezone. Thread text is limited to 2,000 characters per message.

Only text is sent. Attachments, voice notes, Channels, Communities, Broadcasts and business-template management are not exposed.

Gmail

Send from the connected mailbox using REST:

curl -X POST https://api.routergrowth.com/v1/run \
  -H "Authorization: Bearer $ROUTERGROWTH_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: gmail-introduction-001" \
  -d '{
    "capability":"gmail.send",
    "input":{
      "account_id":"work",
      "to":["recipient@example.com"],
      "subject":"Requested information",
      "text":"Hello,\n\nHere is the information you requested."
    },
    "routing":{"max_cost":"0.02"}
  }'

Supply text or html. HTML takes precedence when both are present; plain text is escaped and line breaks are preserved. Optional cc and bcc are arrays of email addresses. At most 50 recipients are accepted across all three recipient lists. The connected mailbox determines the sender.

Read or search messages, then reply:

routergrowth run -c gmail.messages -i '{"account_id":"work","limit":20}' --max-cost 0.01 --wait 30
routergrowth run -c gmail.messages -i '{"account_id":"work","search":"Requested information","from":"recipient@example.com"}' --max-cost 0.01 --wait 30
routergrowth run -c gmail.messages -i '{"account_id":"work","message_id":"EMAIL_ID"}' --max-cost 0.01 --wait 30
routergrowth run -c gmail.send -i '{"account_id":"work","to":["recipient@example.com"],"in_reply_to":"EMAIL_ID","text":"Thanks, received."}' --max-cost 0.02 --wait 30

Use the email's message_id returned by gmail.messages for in_reply_to. The email must belong to the selected mailbox. If you omit subject on a reply, the original subject is reused. Recipients must still be supplied explicitly.

A send returns tracking_id and, when available, provider_id. The tracking ID is not an email ID: list emails to obtain message_id. Listing includes sent and received email, with full text and HTML bodies when available. Supported list filters are search, from, to, folder, thread_id, after, limit and cursor. message_id selects a single email instead of listing.

Attachments, drafts, label changes, deletion and Calendar operations are not exposed.

Send limits

  • Pacing. Sends from one LinkedIn or Instagram account keep a minimum gap and a daily ceiling that rises as the account ages; the day starts again at 00:00 UTC. LinkedIn invitations go out at least 60 seconds apart, 20 a day in the account's first week, then 30, and 180 a week. Comments go out at least 2 minutes apart, 10 a day in the first week, then 20, and one top-level comment per post: a second one from the same account within 90 days ends as a blocked run with 409 repeat_touch (a reply in a thread is not counted). LinkedIn and Instagram messages have ceilings of their own. A send past a limit ends as a blocked run with 429 paced and details.retry_after, nothing sent or charged. The full table is under send pacing. WhatsApp and Gmail sends are not paced by RouterGrowth.
  • The networks' own limits. LinkedIn, Instagram, WhatsApp and Google keep limits of their own, unpublished and tighter on a new account: about 100 LinkedIn profile views and 1,000 search results a day, about 100 Instagram actions a day and 10 an hour, Google's sending quotas. A send the network refuses for a limit comes back provider_rate_limited: stop, and send again hours later. Sends are never retried for you.
  • Recipients. A person who opted out with RouterGrowth itself is blocked on every channel (403 opted_out). With tables on, so is anyone on the workspace's suppression list (403 suppressed), and a new conversation with someone contacted on the same channel inside the repeat window, 30 days by default (409 repeat_touch, see repeat first touch). Each is a blocked run, nothing charged.

The account holder is the sender of record and accepts the network's terms on automation. Replies, new LinkedIn connections and dropped sessions arrive as events and webhooks, one stream for every account.

Billing and retries

Prices on this page are catalog prices, which start at the Scale plan rate; inspect returns your workspace's exact price.

  • The seat. Each connected account is charged every 30 days at your workspace's rate: $7.15 on the Scale plan, $11.00 on pay per call, the other plans in between. The first period is charged to your balance the moment the account connects, then every 30 days after, until it is disconnected. For the exact figure your workspace pays, which is what to show a user before they approve a connection, inspect the network's .account capability and read billing.note; the same amount is seat_price on the account listing below. charged_through on .accounts shows the paid period, and the wallet ledger records each period as a subscription_charge.
  • Calls. Listing accounts, connection links, reconnection, status checks and linkedin.invitations_sent are free. A successful send (an invitation, a message, a comment, an email from Gmail) is $0.0065; a search, a profile lookup or an inbox read is $0.001485. An empty inbox is a successful read. Failed and refused sends are not billed, and neither is a miss: a profile not found, a number that is not on WhatsApp, a post that is gone or closed to comments.
  • An unpaid seat. If the balance cannot cover a seat's charge, on connection or at renewal, the charge is skipped rather than taking the balance below zero, and the account is marked unpaid (unpaid_since). It keeps working, and the charge goes through within the hour after a top-up. An account left unpaid for 7 days is disconnected.
  • A dropped login (CREDENTIALS) is not charged again while it is down. Reconnecting it under the same name costs nothing inside the period already paid; after that period, a new one starts the day it reconnects. If the same person signs in under a new name instead, the new account takes over the paid days rather than being charged twice. A login still down 7 days after its paid period ends is disconnected. An account the provider no longer holds (DISCONNECTED) is not renewed.
  • Disconnecting stops future charges. Days already paid stay with the workspace: the next account connected on the same network starts on them instead of a new charge.

Use a unique Idempotency-Key on REST send calls (--idempotency-key on the CLI, idempotency_key on the MCP run tool) and reuse it when retrying the same operation. Do not retry an uncertain send with a new key: it may have reached the recipient.

Account management API

Method Endpoint Authentication
GET /v1/{network}/accounts API key or dashboard session
POST /v1/{network}/accounts Dashboard session; body contains name and optional return_url
DELETE /v1/{network}/accounts/{name} Dashboard session

{network} is linkedin, instagram, whatsapp or gmail. GET answers the accounts as last recorded (items, count, total, next_step) without a run, with seat_price (amount, currency, period_days): what one connected account costs this workspace per period; the .accounts capabilities also refresh each status from the provider. POST returns a connect link, like .account; its return_url must use the RouterGrowth dashboard origin. DELETE releases the seat and answers {"name": "sales", "disconnected": true, "paid_through_kept": "..."}, where paid_through_kept is the date the paid days run to, or an empty string. API keys and connected apps cannot use POST or DELETE: agents request a connection link with the .account capability, and accounts are disconnected from the dashboard. Disconnecting does not delete the LinkedIn, Instagram or WhatsApp account or the Google mailbox.

Reading this as an agent? This page as markdown: /docs/connected-accounts.md · every page: /docs/llms.txt