Zoho Campaigns

Connect AI agents to Zoho Campaigns. Agents add and unsubscribe mailing list subscribers, read list membership to keep audiences in sync, and list, inspect, and send email campaigns as the final step of a launch workflow.

7 actions OAuth available

Zoho Campaigns website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A product launch reaches its go date, with the announcement campaign already drafted and reviewed in Zoho Campaigns

List Mailing Lists confirms the target list keys and current contact counts

List Subscribers samples the audience and verifies active status filtering looks right

Get Campaign Details pulls the campaign's subject, sender, and associated lists for a final cross-check

The agent compares the campaign's lists against the launch plan and flags any mismatch

The campaign owner reviews the summary, audience size, subject, sender, lists, and gives the go

Send Campaign fires the delivery to the associated mailing lists

What This Integration Enables

Zoho Campaigns is the sending arm of the Zoho suite, and like every email platform, its output is only as good as the list hygiene and launch discipline behind it. That is agent work. FlowRunner agents keep mailing lists synchronized with the systems where subscribers actually appear and disappear, storefronts, forms, CRMs, and treat the campaign send itself as the carefully gated final step of a launch workflow rather than a button someone clicks under deadline pressure. - Add new leads and customers to mailing lists the moment they sign up in another system - Propagate opt-outs across lists as soon as a contact unsubscribes anywhere - Export list membership to data stores and CRMs to keep audiences consistent - Inspect campaign details, status, and list associations before anything sends - Trigger a prepared campaign as the final, approved step of a launch workflow The division of labor matters because Zoho Campaigns deliberately separates authoring from sending: campaigns are drafted and reviewed inside the platform, and the API's Send Campaign fires only what already exists. FlowRunner leans into that design. Agents never compose the email; they own the audience plumbing and the launch mechanics around a campaign that humans wrote and approved, which is exactly the shape of work automation should take off a marketing team's plate. The send button is exactly where FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) discipline lives on this page: agents assemble and verify, a person launches. Subscriber syncs and opt-out propagation run autonomously all day; the moment with consequences gets a named approver and a timestamped yes.

Without FlowRunner

Audiences drift out of sync Signups live in the storefront, opt-outs live in a form tool, and the mailing list reflects neither

Launch sends are a tab-juggling ritual Someone checks the list, the campaign, and the calendar in three windows and hopes they match

Unsubscribes lag A contact opts out in one system and keeps receiving campaigns from another for weeks

With FlowRunner

Lists mirror reality Every signup and every opt-out flows into Zoho Campaigns the moment it happens elsewhere

Launch is a checklist the agent runs Audience, subject, sender, and list associations get verified before anyone is asked to approve

Opt-outs propagate immediately Unsubscribe Contact fires the same day the request lands, on every list it touches

Use Case Scenarios

Every customer becomes a subscriber, correctly

A new order lands in [Shopify](/integrations/shopify). The agent resolves the newsletter list with List Mailing Lists, then calls Add Subscriber with the customer's email and name mapped from the order. If the list is configured for confirmed opt-in, the customer gets the confirmation email and joins on their own say-so. No CSV imports, no lag between becoming a customer and being reachable.

Opt-outs that actually take effect

Opt-out requests arrive through a [Typeform](/integrations/typeform) form, and some arrive as replies the support team forwards along. The agent reads each response and calls Unsubscribe Contact for the respondent on every relevant list, then logs the email and timestamp to [Google Sheets](/integrations/google-sheets). When a compliance question comes later, the sheet shows the request and the same-day unsubscribe side by side. The contact stays in the account, marked unsubscribed, exactly as the platform intends.

The launch that checks itself

Launch day. The campaign was drafted and reviewed in Zoho Campaigns days ago. The agent runs the preflight: Get Campaign Details confirms subject, sender, and associated lists; List Subscribers confirms the audience count matches expectations; a mismatch on any of them halts the flow. The summary posts to [Slack](/integrations/slack) for the campaign owner, who replies with approval. Send Campaign fires, and the send record, campaign key, audience size, approver, timestamp, lands in the launch log. Next launch, the same preflight runs again, because the checklist is a workflow now, not a memory.

Human-in-Loop Highlight

Send Campaign triggers delivery to every subscriber on the campaign's associated mailing lists, and once the send begins it cannot be undone. There is no unsend in email marketing; a campaign that goes to the wrong list, or goes twice, is apologized for, not recalled. So a FlowRunner launch workflow does everything except press the button. The agent verifies the campaign key against the launch plan, pulls the audience size, confirms the subject and sender, and presents the whole picture to the campaign owner: this campaign, these lists, this many contacts. Only the owner's explicit approval releases the send. The agent removes every reason a launch gets fumbled; it never removes the person from the moment that matters.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

7 actions

Mailing Lists

List Mailing Lists Retrieves your mailing lists with each list's key, name, and contact count, with sorting and pagination. The resolution step before any subscriber or campaign operation.

Subscribers

List Subscribers Retrieves a list's contacts with email, name, and status, filterable by active, unsubscribed, bounced, and more. Used for audience verification and syncing membership to other systems.
Add Subscriber Adds a contact to a mailing list by list key and email, with optional name and merge fields. Depending on list settings, the contact confirms by email before becoming active.
Unsubscribe Contact Marks a contact unsubscribed for a list so they no longer receive its campaigns, while remaining in your account. The action that makes opt-outs propagate instead of lag.

Campaigns

List Campaigns Retrieves campaigns with key, name, subject, and status, filterable by sent, scheduled, in progress, and more. Used to locate the campaign a workflow is about to act on.
Get Campaign Details Retrieves a campaign's full detail, name, subject, sender, status, associated lists, and schedule. The preflight read before any send decision.
Send Campaign Immediately sends an existing, ready-to-send campaign to its associated mailing lists. Delivery cannot be undone once it begins. The action this page's human gate exists for.

Frequently Asked Questions

What can FlowRunner do with Zoho Campaigns?

FlowRunner agents can run List Mailing Lists, List Subscribers, and Add Subscriber in Zoho Campaigns, plus 4 more actions.

Does connecting Zoho Campaigns to FlowRunner require OAuth?

Yes. Zoho Campaigns connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can Zoho Campaigns trigger a FlowRunner workflow automatically?

Zoho Campaigns doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Zoho Campaigns

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us