Zapier social media automation: Instagram, TikTok, Facebook and more
easyCoexistence connects Zapier to Instagram, TikTok, Facebook, YouTube and more channels, each through its official API. Instagram and Facebook comments, mentions and DMs, and TikTok comments, trigger a Zap through a Webhooks by Zapier catch hook. MCP Client by Zapier runs easyCoexistence's MCP tools to publish, reply and read analytics, and webhook actions call a network's API with fresh credentials.
The MCP Client by Zapier action that runs a tool on a remote MCP server and returns one result.
The MCP Client connection setting for a server that signs in with OAuth; Zapier then ignores the bearer token field.
The largest body Catch Raw Hook accepts, handed to the Zap unparsed and with the request headers.
What Zapier's Python code steps include, along with requests, so hmac and hashlib can check a signature.
MCP tools behind one easyCoexistence connector, reachable from a Zap through the Run tool action.
What can a Zap do on each network?
Each network gives a Zap a trigger and a set of actions, through easyCoexistence and the network's official API:
- Instagram: a comment, mention or DM triggers the Zap, which can publish photos, carousels, Reels and Stories, reply in public or by DM, hide comments and read insights.
- Facebook: comments and other Page feed activity, Messenger messages and mentions trigger it; it can publish Page posts, reply in public or in Messenger, hide comments and read insights.
- TikTok: a comment triggers it, and it can publish videos and photo posts, reply to comments in public, hide them and read account and video metrics.
- YouTube: Schedule by Zapier starts it on a timer, and it can upload videos, reply to and moderate comments and read YouTube Analytics.
- LinkedIn: Schedule by Zapier starts it too, and it can comment, reply and read statistics. LinkedIn posts stay out of Zaps: an agent drafts each one on request, for example in Claude or ChatGPT, and a person approves it.
How does a comment or DM trigger a Zap?
Start the Zap with Webhooks by Zapier and choose Catch Raw Hook, which passes on the request headers with the body unparsed: the two things a signature check needs. Copy the URL Zapier generates and point the account at it with set_social_webhook_destination, from Claude or ChatGPT or once through MCP Client by Zapier, or with PUT /api/v1/channels/:id/webhook on the Partner API. The account's signing secret comes back once.
Each forwarded event shares an envelope: platform, account_id, external_id and entry, where entry is the network's own event. A comment on a Facebook Page arrives like this, and the Code step described below turns it into fields the rest of the Zap can map:
{
"platform": "facebook",
"account_id": "<ACCOUNT_ID>",
"external_id": "<PAGE_ID>",
"entry": {
"id": "<PAGE_ID>",
"time": 1793318400,
"changes": [
{
"field": "feed",
"value": {
"item": "comment",
"verb": "add",
"comment_id": "<COMMENT_ID>",
"post_id": "<PAGE_POST_ID>",
"from": { "id": "<USER_ID>", "name": "<NAME>" },
"message": "Is this still available?"
}
}
]
}
}How does a Zap use the easyCoexistence MCP server?
Through MCP Client by Zapier, a beta app for using remote MCP servers in Zapier. Add a connection with https://easycoexistence.com/api/mcp as the server URL, Streamable HTTP as the transport and OAuth set to Yes, then sign in to easyCoexistence and grant Zapier access.
Its Run tool action calls one tool by name, with arguments mapped from earlier steps: reply_to_comment with the account_id, the comment's ID and the text, or send_social_dm with the sender's ID. Publishing works the same way, with publish_instagram_post, publish_facebook_post, publish_tiktok_post or upload_youtube_video. Zapier documents how the action reports its result in Agents as well as in Zaps.
How does a Zap call a network's API with fresh credentials?
With two Webhooks by Zapier actions. The first, a GET, fetches /api/v1/channels/<account_id>?credentials=1 from easyCoexistence, with an Authorization header holding a Partner API key from the dashboard. Its answer has the network's API base, the account's ID on the network and, on TikTok, YouTube and LinkedIn, an access token easyCoexistence keeps renewed. The second, a Custom Request, calls the network with that token, sent the way the network expects; the credentials come with example calls.
This covers what the MCP tools leave out, and suits YouTube and LinkedIn, where a Zap started by Schedule by Zapier reads new comments. For a YouTube channel, a GET on commentThreads with the channel's ID returns its comment threads.
GET https://easycoexistence.com/api/v1/channels/<ACCOUNT_ID>?credentials=1
Authorization: Bearer ec_live_…
{
"id": "<ACCOUNT_ID>",
"channel": "youtube",
"status": "connected",
"credentials": {
"platform": "youtube",
"api_base": "https://www.googleapis.com/youtube/v3",
"channel_id": "<YOUTUBE_CHANNEL_ID>",
"access_token": "<CURRENT_TOKEN>",
"token_expires_at": "<EXPIRY>"
}
}How do you verify the signature in a Zap?
Add a Code by Zapier step in Python right after the catch hook. Zapier's Python steps include the standard library, so hmac and hashlib are there without installing anything. Map three values into the step's input data: the raw body, the X-EC-Signature header and the account's signing secret.
The code splits the header into t and v1, computes an HMAC-SHA256 over the timestamp, a dot and the raw body, compares the two in constant time and checks the timestamp is less than 5 minutes old. It returns valid with the fields later steps need, and a Filter by Zapier step lets the Zap continue only when valid is true.
import hashlib, hmac, json, time
raw = input_data["raw_body"]
sig = dict(part.split("=", 1) for part in input_data["signature"].split(","))
expected = hmac.new(
input_data["secret"].encode(),
f"{sig['t']}.{raw}".encode(),
hashlib.sha256,
).hexdigest()
fresh = abs(time.time() - int(sig["t"])) < 300
event = json.loads(raw)
output = {
"valid": hmac.compare_digest(expected, sig.get("v1", "")) and fresh,
"platform": event["platform"],
"account_id": event["account_id"],
}What do the networks require of a Zap?
Each network's API sets rules a Zap has to follow:
- Media: images and videos are fetched from a public HTTPS link, so upload them first. Instagram publishes JPEG images, and TikTok photo posts take JPEG or WebP.
- TikTok publishing: TikTok downloads media only from URL prefixes verified for the publishing app, so use
publish_tiktok_post, which serves your file to TikTok from easyCoexistence's verified media route. - DMs: Instagram Direct and Messenger accept a reply only within 24 hours of the person's last message.
- TikTok replies: there are no DMs on TikTok, so the Zap replies to TikTok comments in public, under the comment.
- Tokens: TikTok and YouTube tokens expire and easyCoexistence renews them, so fetch credentials in each run rather than pasting a token into a step.
Common mistakes
- Turning the Zap off while events still point at its hook. Zapier answers 404 to a Zap that is off, and each event is forwarded only once, so those comments are gone.
- Choosing Catch Hook when the Zap checks signatures. Catch Hook parses the body, and the HMAC has to be computed over the raw text that Catch Raw Hook keeps.
- Calling the Partner API with the MCP sign-in. The MCP connection uses OAuth, while the Partner API takes a key beginning ec_live_ in an Authorization header.
- Replying to the Page's own comments. The Zap's replies come back as feed events, so skip comments whose from.id is the Page's own ID.
easyCoexistence gives your Zaps and Zapier agents reach to customers on Instagram, Facebook, TikTok, YouTube and more channels, each on its official API: signed events for a catch hook, 35+ MCP tools for MCP Client by Zapier and fresh credentials for webhook actions. US$ 9 to US$ 0.75 per connection per month, falling as you add connections, with the first 3 days free.
easyCoexistence is a multichannel API and MCP server that connects AI agents such as Claude and ChatGPT to WhatsApp, Instagram, TikTok, Facebook and more. On WhatsApp it uses Coexistence: the business keeps using its number in the WhatsApp Business app while the AI works through Meta's official API.
Frequently asked questions
Can Zapier use the easyCoexistence MCP server?
Yes, with MCP Client by Zapier, a beta app. Connect https://easycoexistence.com/api/mcp with Streamable HTTP and OAuth set to Yes, sign in, then call tools from a Zap with the Run tool action.
Can a Zap reply to Instagram comments?
Yes. Run tool calls reply_to_comment with the account_id and the comment's ID from the event. With private set to true it sends the commenter a DM instead, once per comment and within 7 days of it.
Which Zapier plan do I need?
One that includes Webhooks by Zapier, which Zapier lists on its Professional, Team and Enterprise plans and not on Free.
How much does easyCoexistence cost?
US$ 9 to US$ 0.75 per connection per month, falling as you add connections, the same on each network. The MCP server and the Partner API are part of it, and the first 3 days are free.
Keep reading
Connect your first channel in two minutes.
No platform reviews to wait for. Connect WhatsApp, Instagram, TikTok or another channel, then ask your AI to post, reply or report, and watch it work.
- 3 days free
- Cancel any time
- Official APIs only
- Monitored 24/7
Verified on