Skip to content
ClickRuntime

Automate Omnisend

Know who is joining your Omnisend audience and how your campaigns land, without checking the store dashboard. New contacts are posted for the team, sign-ups are counted each morning, and campaign results arrive every week. Describe what you want to your AI assistant, check what it will do, and it keeps running with your laptop closed.

Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Try asking

Create a ClickRuntime automation: every 15 minutes, check Omnisend for new contacts and post each one's email to #store in Slack.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Ideas

What you can automate in Omnisend

New contacts reported within minutes, a morning count of yesterday's sign-ups, and a weekly email on the campaigns you sent. These are ready-made starting points. Anything else you can describe works too.
Every 15 minutes

Post new Omnisend contacts to Slack

Your team sees each new contact's email in Slack within minutes of them signing up.

See how it works
Daily

Get a morning email of yesterday's Omnisend sign-ups

Each morning you see how many contacts joined, who they are and how that compares with last week.

See how it works
Weekly

Get last week's Omnisend campaigns in one email

Each Monday you get a summary of the campaigns sent the week before.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with Omnisend, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any Omnisend automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what Omnisend should do in your own words, with your conditions, other apps or an AI step, and your assistant writes it, tests it and runs it on ClickRuntime.

  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

For example, ask your assistant

Every week, find Omnisend contacts who bought once over 90 days ago and tag them for a win-back campaign.

When a Shopify customer places a second order, add a repeat-buyer tag to their Omnisend contact.

When a new Shopify order comes in, update the customer in Omnisend, log the order in a Google Sheet and alert Slack if it is over $500.

Beyond chat

Have Omnisend work when you're not in the chat

Connecting Omnisend to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Setup

Connect Omnisend

You connect Omnisend with an API key you create in your own store settings.

Omnisend

Ecommerce email/SMS

  1. In Omnisend, open Store settings, then API keys.
  2. Choose Create API key and give it a name you'll recognise.
  3. Copy the key.
  4. In the ClickRuntime dashboard, open Connections & secrets and save the key as a secret for Omnisend.

Good to know

Omnisend limits that affect automations

  • Each API key belongs to one Omnisend store. For a second store, create a key there.
  • The new contact alert checks for contacts every 15 minutes rather than the moment they sign up.
  • Omnisend's API is versioned. Older guides mention an X-API-KEY header, but current calls use the Omnisend-API-Key header instead.

FAQ

Questions about automating Omnisend

What can ClickRuntime see in my Omnisend store?
What your API key allows. The automations here read contacts and campaigns. They don't send campaigns or change contacts.
How soon do new contact alerts arrive?
Within about 15 minutes. The automation checks for contacts created since its last check and posts only the new ones, so nobody is reported twice.
What's in the morning sign-up email?
How many contacts joined yesterday, who they are, and how that compares with the week before.
I found guides that use an X-API-KEY header. Is that wrong?
Those are for older API versions. Your key works with the newer versioned header, which is what ClickRuntime uses.
Do I need AI for Omnisend automations?
No. These run without it. If you want a written summary or a short comment on the numbers, that uses the AI that comes with every ClickRuntime plan, so you don't need your own AI key.
Is this a Omnisend connector for ChatGPT or Claude?
Not for chatting with Omnisend data. A chat connector lets your assistant read and change Omnisend while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each Omnisend event.

Related pages

Keep exploring

Tell your assistant what Omnisend should do

Free plan. No credit card.

Add to ChatGPTAdd to Claude