Zernio MCP logo

Integrate Zernio MCP with your AI CRM

Zernio is a social media management API for scheduling posts, pulling analytics, managing inbox conversations and running ads across 14+ platforms including Facebook, Instagram, LinkedIn, TikTok, X, YouTube, Reddit, Pinterest, WhatsApp Business and Telegram.

Explore Triggers and Actions

Account groups list account groups

List groups

ActionTry it

Accounts get

Get account details for a specific platform. Returns username and ID for the first account matching the platform.

ActionTry it

Accounts get account health

Check account health

ActionTry it

Accounts get all accounts health

Check accounts health

ActionTry it

Accounts get follower stats

Get follower stats

ActionTry it

Accounts list

List all connected social media accounts. Returns the platform, username, and account ID for each connected account. Use this to find account IDs needed for creating posts.

ActionTry it

Accounts move account to profile

Move account to another profile

ActionTry it

Analytics get analytics

Get post analytics

ActionTry it

Analytics get best time to post

Get best times to post

ActionTry it

Analytics get daily metrics

Get daily aggregated metrics Args: platform: Filter by platform (e.g. "instagram", "tiktok"). Omit for all platforms. profile_id: Filter by profile ID. Omit for all profiles. account_id: Filter by account ID from_date: Inclusive start date (ISO 8601). Defaults to 180 days ago. to_date: Inclusive end date (ISO 8601). Defaults to now. source: Filter by post origin. "late" for posts published via Zernio, "external" for posts imported from platforms. attribution: How each post's engagement is attributed to a day. "publish" (default) sums each post's lifetime total on its publish date. "received" buckets the per-day increase in engagement by the day it actually arrived (engagement-over-time), so engagement on older posts appears on the day it was gained rather than the post's publish date.

ActionTry it

Analytics get post timeline

Get post analytics timeline Args: post_id: The post to fetch timeline for. Accepts an ExternalPost ID, a platformPostId, or a Zernio Post ID. (required) from_date: Start of date range (ISO 8601). Defaults to 90 days ago. to_date: End of date range (ISO 8601). Defaults to now.

ActionTry it

Call tool

Call a tool by name with the given arguments. Use this to execute tools discovered via search_tools.

ActionTry it

Comments get inbox post comments

Get post comments

ActionTry it

Comments list inbox comments

List commented posts

ActionTry it

Comments reply to inbox post

Reply to comment

ActionTry it

Docs search

Search across the Late API documentation to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Late, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with section titles and relevant snippets.

ActionTry it

Media check upload status

Check the status of an upload token and get uploaded file URLs. Use this after the user has uploaded files through the browser upload page. Returns: pending (waiting for upload), completed (files ready), or expired (token expired).

ActionTry it

Media generate upload link

Generate a unique upload URL for the user to upload files via browser. Use this when the user wants to include images or videos in their post. The flow is: 1. Call this tool to get an upload URL 2. Ask the user to open the URL in their browser 3. User uploads files through the web interface 4. Call media_check_upload_status to get the uploaded file URLs 5. Use those URLs when creating the post with posts_create

ActionTry it

Mentions list inbox mentions

List mentions

ActionTry it

Mentions reply to mention

Reply to a mention

ActionTry it

Posts bulk upload posts

Bulk upload from CSV Args: dry_run

ActionTry it

Posts create

Create a social media post. Can be saved as DRAFT, SCHEDULED, or PUBLISHED immediately. ⚠️ IMPORTANT - Choose the correct mode based on user intent: **DRAFT MODE (is_draft=True)** Use when user says: "draft", "borrador", "save for later", "don't publish", "save it", "guardar" → Post is saved but NOT published and NOT scheduled. User can edit it later. **IMMEDIATE MODE (publish_now=True)** Use when user says: "publish now", "post now", "publica ya", "immediately", "right now", "ahora" → Post goes live IMMEDIATELY. **SCHEDULED MODE (default)** Use when user says: "schedule", "programar", "in X minutes/hours", "at 3pm", "tomorrow" → Post is scheduled for future publication. Use schedule_minutes to set the delay. ⚠️ MULTI-ACCOUNT USERS (agencies, multi-client setups): If the user has more than one account on the target platform, you MUST pass `account_id`. Call `accounts_list` (or `profiles_list` then `accounts_list`) first to discover the right ID. If you omit account_id when multiple accounts exist, the tool returns an error listing the candidates - use it to retry. Examples: - "Create a draft tweet" → is_draft=True - "Post this to Twitter now" → publish_now=True - "Schedule a LinkedIn post for 2 hours from now" → schedule_minutes=120 - "Post this to Acme's Twitter" → call accounts_list, find Acme's twitter ID, pass account_id

ActionTry it

Posts cross post

Post the same content to multiple platforms at once. ⚠️ IMPORTANT - Choose the correct mode based on user intent: **DRAFT MODE (is_draft=True)** Use when user says: "draft", "borrador", "save for later", "don't publish" → Posts are saved but NOT published. User can edit them later. **IMMEDIATE MODE (publish_now=True)** Use when user says: "publish now", "post now", "immediately" → Posts go live IMMEDIATELY on all platforms. **SCHEDULED MODE (default)** Use when user says: "schedule", "programar", "in X hours" → Posts are scheduled for 1 hour from now. ⚠️ MULTI-ACCOUNT USERS: - To pick a specific account per platform, pass `account_ids` parallel to `platforms` (same order, comma-separated). Use empty string for a position to fall back to profile/auto-resolution. - To target multiple accounts of the SAME platform in one call, repeat the platform: platforms='twitter,twitter', account_ids='acc_a,acc_b'. - If you omit account_ids and the user has multiple accounts for any of the requested platforms, the tool errors with the candidate list - use it to retry.

ActionTry it

Posts delete

Delete a post by ID. Published posts cannot be deleted.

ActionTry it

Posts edit post

Edit published post

ActionTry it

Posts get

Get full details of a specific post including content, status, and scheduling info.

ActionTry it

Posts list

List posts with optional filtering by status. Status options: draft, scheduled, published, failed

ActionTry it

Posts list failed

List all failed posts that can be retried.

ActionTry it

Posts publish now

Publish a post immediately to a platform. The post goes live right away. Use this when user explicitly wants to publish NOW, not schedule for later. This is a convenience wrapper around posts_create with publish_now=True. ⚠️ MULTI-ACCOUNT USERS: pass `account_id` when the user has more than one account on this platform. Call `accounts_list` first to find the right ID.

ActionTry it

Posts retry

Retry publishing a failed post. Only works on posts with 'failed' status.

ActionTry it

Posts retry all failed

Retry all failed posts at once.

ActionTry it

Posts unpublish post

Unpublish post

ActionTry it

Posts update

Update an existing post. Only draft, scheduled, and failed posts can be updated. Published posts cannot be modified.

ActionTry it

Profiles create

Create a new profile for grouping social accounts.

ActionTry it

Profiles delete

Delete a profile. The profile must have no connected accounts.

ActionTry it

Profiles get

Get details of a specific profile including name, description, and color.

ActionTry it

Profiles list

List all profiles. Profiles group multiple social accounts together for easier management.

ActionTry it

Profiles update

Update an existing profile. Only provided fields will be changed.

ActionTry it

Queue create queue slot

Create schedule

ActionTry it

Queue delete queue slot

Delete schedule

ActionTry it

Queue get next queue slot

Get next available slot

ActionTry it

Queue list queue slots

List schedules

ActionTry it

Queue preview queue

Preview upcoming slots

ActionTry it

Queue update queue slot

Update schedule

ActionTry it

Search tools

Search for tools using natural language. Returns matching tool definitions ranked by relevance, in the same format as list_tools.

ActionTry it

Tracking tags get tracking tag stats

Get aggregated event stats

ActionTry it

Tracking tags list tracking tags

List tracking tags

ActionTry it

Usage get usage

Usage snapshot (default) or billed-spend metering (with params) Args: reconcile: Snapshot mode only. For Stripe subscription users, `true` forces a subscription reconciliation pass even when cached plan data looks complete. range: Window to report. `cycle` / `prev-cycle` resolve to the customer's real billing-period bounds (falling back to a trailing 30 days when no invoice exists yet); `7d`…`12mo` are trailing windows; `custom` uses `from` / `to`. from_: Inclusive start (UTC date). Required when `range=custom`. to: Inclusive end (UTC date). Required when `range=custom`. Max span 366 days. granularity: Bucketing of the `days` series: `day` (one row per UTC day), `month` (one row per calendar month, dated to the 1st), or `total` (no series, read `totals`). Does not affect `totals`. group_by: Metering mode. Adds `attribution`: the window's spend split per profile or per account (keys are ids; resolve names via `GET /v1/profiles` / `GET /v1/accounts`). profile_id: Metering mode (pair with `range`). Project the payload onto this profile's attributed share. Mutually exclusive with `accountId`, and `groupBy` (if given) must be `profile`; 404 when the profile is not in your team (or outside a scoped key's profiles). account_id: Metering mode (pair with `range`). Project the payload onto this account's attributed share. Mutually exclusive with `profileId`, and `groupBy` (if given) must be `account`; 404 when the account is not visible to the caller.

ActionTry it

Validate media

Validate media URL

ActionTry it

Validate post

Validate post content

ActionTry it

Validate post length

Validate character count

ActionTry it

Zernio overview

Show an overview of what this Zernio MCP server can do (accounts, posts, analytics, ads, inbox) and how to find the right tool.

ActionTry it

How the Zernio MCP integration works

The Zernio MCP integration connects your Dench AI CRM directly to Zernio MCP, so agents can read and act on your Zernio MCP data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.

52 actions are available for agents to invoke on your behalf. Every call runs through Zernio MCP's own authorization, scoped to the account you connect.

Set up Zernio MCP in Dench

  1. 1

    Sign in to your Dench workspace and open Integrations.

  2. 2

    Find Zernio MCP and click Connect — you'll authorize access through Zernio MCP's own sign-in flow. No API keys or code required.

  3. 3

    Ask an agent to use Zernio MCP in chat, or call it from an automation.

  4. 4

    Manage or disconnect the connection any time from workspace settings.

Frequently asked questions

How does the Zernio MCP integration work with Dench?

The Dench Zernio MCP integration connects your AI CRM to Zernio MCP, so AI agents can work with your Zernio MCP data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.

What actions can AI agents perform with Zernio MCP via Dench?

The Zernio MCP integration currently exposes 52 actions, including Account groups list account groups, Accounts get, Accounts get account health, Accounts get all accounts health, Accounts get follower stats, and Accounts list. Agents invoke them on your behalf from chat or from automations.

Do I need to write code to connect Zernio MCP to Dench?

No. You connect Zernio MCP from your Dench workspace using Zernio MCP's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.

Is the Zernio MCP integration secure?

Connections are authorized through Zernio MCP's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Zernio MCP connection from your workspace settings at any time.

Zernio MCP | Dench AI CRM