Connect

Integrations and API: Canva, Drive, Zapier, MCP and More

Updated October 27, 2026 · Multi Post Social guide

What integrations do in Multi Post Social

Integrations in Multi Post Social fall into four groups. Media integrations bring images and videos into the composer from where they already live. Automation integrations let another service create posts, read analytics or react to events without anyone typing. Team integrations push notifications and content to the places your team already looks. Developer access, through the API, webhooks and MCP, lets you build anything the first three groups do not cover.

Every integration is connected from Settings, under Connected apps. You see each one with its status, the permissions it holds and the date it was last used, and you can disconnect any of them with one click. Integrations are per workspace, so an agency can connect a client’s Canva account to that client’s workspace only.

Design and media: Canva, Unsplash and cloud storage

The composer has a media button with tabs for each connected source. Canva opens your designs in a picker; choose one and it is exported at the size of the first selected network, with a resize option for the others. Unsplash searches free stock photos and inserts them with the photographer credit prepared as alt text or a first comment. Google Drive, Dropbox and OneDrive browse your folders, and files you pick are copied into the post so a later move in the drive does not break anything. Google Photos is available for personal accounts.

Each media file goes through the same checks as an upload: size, aspect ratio and length for the formats you chose, and a prompt for alt text. The image size guide lists the sizes the composer will ask for.

Automation: Zapier, Make, n8n and IFTTT

Automation integrations let you say “when this happens there, do that here” without code. Multi Post Social provides a native app on Zapier and Make, a community node for n8n, and a service on IFTTT. Each exposes the same triggers and actions.

Triggers you can react to

• Post published, post failed, post approved, post needs approval.
• New inbox item, inbox item labeled, inbox item assigned.
• New mention in a listening stream, stream alert fired.
• Channel disconnected, weekly report ready.

Actions you can take

• Create a draft or add a post to the queue for one or more channels, with media by URL.
• Add an idea to the Create board with tags.
• Reply to an inbox item or add a label.
• Fetch analytics for a channel and date range.

Popular recipes include “new blog post in WordPress adds a draft to the queue,” “new row in a spreadsheet becomes a scheduled post,” and “failed post opens a ticket in the help desk.” Because actions create drafts or queue items, a human still presses publish or the queue publishes at a slot you set.

Team tools: Slack, WordPress and Bitly

Slack receives the notifications you choose in a channel of your choosing: published posts with a link, failures with the reason, approval requests with Approve and Request changes buttons that work from Slack, and inbox items that match a label. WordPress works in both directions: a plugin adds a “share to Multi Post Social” box on the post editor, and the automation triggers above can create a queue item for every new article. Bitly can replace the built-in link shortener if your team already uses branded short links; UTM tags from the UTM builder are kept.

Every integration at a glance

The REST API and API keys

The API is the same one the web app uses, documented at the API documentation page. It is a JSON REST API over HTTPS with endpoints for posts, channels, media uploads, inbox items, streams, mentions, analytics and workspaces. Authentication uses API keys that you create in Settings under API. Each key has a label, a set of scopes such as posts:write or analytics:read, and an optional list of allowed workspaces. The full key is shown once at creation; afterwards only its prefix is visible, so store it in a secrets manager.

Keys can be rotated without downtime: create the new key, deploy it, then revoke the old one. Every call is recorded in the activity log with the key prefix, which helps when several integrations share an account. The developers guide has a getting-started walkthrough with code samples.

A first call takes a minute. Send a GET request to the channels endpoint with your key in the Authorization header and you get back a list of connected channels with their ids, networks and posting schedules. Send a POST to the posts endpoint with a channel id, text and an optional scheduled time, and the post appears in the queue or in Drafts, depending on the key’s scopes and the approval settings of the workspace. Media is uploaded in two steps, request an upload URL, then PUT the file, so large videos never pass through the API server. Responses are paginated with a cursor, dates are ISO 8601 in UTC, and every error carries a code and a plain-language message. The API has a versioned path, and old versions keep working for at least twelve months after a new one ships.

Webhooks

Webhooks push events to a URL you control the moment they happen, which is faster and cheaper than polling the API. You register an endpoint, choose events, and receive a signed JSON payload for each one. The signature uses a secret shown at registration; verify it before trusting a payload. Failed deliveries are retried with backoff for 24 hours, and the webhook page shows the last 100 deliveries with their status codes so you can debug without logs on your side. Webhooks are included from the Essentials plan.

The MCP server for AI agents

MCP, the Model Context Protocol, is an open standard that lets AI assistants such as Claude or ChatGPT use tools. Multi Post Social runs an MCP server so an agent you already use can work with your workspace. Connect it with an API key scoped to what you want the agent to see. The agent can then answer questions like “which of our posts in the last six months earned the most saves?”, draft a week of posts in your tone, propose posting times from your best-time data, and summarize the inbox.

The important line is where the agent stops. By default the MCP server allows reading and creating drafts. An agent can put posts into Needs approval or into Drafts; it cannot publish, schedule or reply unless you grant the posts:publish scope on purpose. Most teams never grant it. You review the drafts in the composer, like any other content, and press Add to queue yourself. The MCP specification describes the protocol, and the AI assistant guide explains how in-product AI and external agents differ.

API limits per plan

Limits exist to keep the service fast for everyone. They are generous for normal integrations and visible on the API settings page as a live usage bar. Hitting a limit returns a clear error with the reset time; it never deletes or fails a scheduled post.

Media uploads and analytics exports count as one request each. Webhook deliveries do not count against your limit. See pricing for everything else that changes between plans.

Popular automation recipes

Most teams use integrations for a handful of repeatable jobs. These recipes work on Zapier, Make, n8n and IFTTT alike, because they use the same triggers and actions. Each one takes about ten minutes to set up and runs without attention afterwards.

• Blog to queue. Trigger: new post published in WordPress or any RSS feed. Action: create a draft for LinkedIn, X and Facebook with the title, the excerpt and the featured image. Approvals stay on, so an editor presses Add to queue after a read.
• Spreadsheet to calendar. Trigger: new row in a sheet with columns for date, time, channels, text and image URL. Action: schedule the post. Useful for quarterly plans written by people who never open the social media scheduler.
• Failed post to ticket. Trigger: post failed. Action: open a ticket in the help desk with the failure reason and a link to the post. The community manager sees it next to customer tickets.
• Negative mention to Slack. Trigger: new mention with negative sentiment in a listening stream. Action: Slack message to the brand channel with the text and a reply link. The listening guide explains how sentiment is scored.
• Approval to calendar invite. Trigger: post approved with a scheduled time. Action: add a calendar event for the author so they are online to answer comments when it publishes.
• Weekly report to the team. Trigger: weekly report ready. Action: post a summary to Slack and email the PDF to stakeholders who do not log in.
• New review to inbox label. Trigger: new review on Google Business Profile. Action: label it Review and assign it to the owner, so reviews are answered within a day.

Choosing between no-code, webhooks and the API

All three routes reach the same data, so the choice is about who maintains the connection and how fast it must react. No-code platforms suit marketing teams: a drag-and-drop editor, hosted for you, with a monthly task quota on their side. They react within a minute or two of an event. Webhooks suit teams with a developer and their own service: instant, free of per-task fees, and able to carry any logic you can write, at the cost of hosting an endpoint and verifying signatures. The REST API suits scheduled jobs and anything that needs to read a lot of data, such as a nightly analytics sync into a data warehouse or a custom dashboard.

A common pattern mixes them: webhooks tell your service that something happened, the API fetches the details it needs, and a no-code platform handles the two or three notifications the marketing team wants to tweak without filing a ticket. Whatever you choose, keep the number of integrations small enough that someone can list them from memory. Connected apps you cannot name are the ones that break quietly.

Step by step: connect your first integrations

1. Open Settings, then Connected apps. Connect Canva and your cloud storage first; they save the most time in the composer.
2. Connect Slack and choose a channel. Turn on Post failed and Needs approval notifications.
3. Create an API key with the scopes you need, label it after the tool that will use it, and store it in a secrets manager.
4. Build one automation. In Zapier or Make, start with “new blog post creates a draft in the queue” and test it with one article.
5. Register a webhook if you run your own service, verify the signature, and send a test event from the webhook page.
6. Connect an AI agent through MCP with a read-and-draft key. Ask it for last month’s top posts to confirm the connection works.
7. Review Connected apps monthly. Disconnect anything unused and rotate keys older than a year.

Benefits and limits of integrations

The benefits of integrations are speed and fewer copies. Designs arrive without downloads, articles become drafts without pasting, failures reach the team where they already work, and developers can build exactly what a team needs. Agencies especially value the per-workspace connections, which keep client accounts apart.

The limits are honest ones. An automation that creates posts can also create many bad posts quickly, so keep approvals on for automated drafts. Third-party services change their APIs; when one does, the connection may need a reconnect, and the Connected apps page tells you. Rate limits apply across all keys in a workspace. And an integration never changes what a network allows; a post that breaks a network’s rules fails the same way whether a person or a script created it.