Integration
Connect CleverReach and Swiftype
When something happens in CleverReach or Swiftype, your agent does the next thing in the other. Describe it and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want CleverReach and Swiftype to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What CleverReach and Swiftype can do together
From CleverReach to Swiftype
When New Campaign in CleverReach
then Add domain in Swiftype
From Swiftype to CleverReach
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with CleverReach and Swiftype
Triggers and actions 4 triggers · 33 actions
- New Campaign
Triggers when a new mailing campaign is created.
- New Subscriber
Triggers when a new subscriber is added to a specified integration list.
- New Unsubscriber
Triggers when any current subscriber unsubscribes from a specified list.
- Add attribute
Create a global attribute.
- Add group
Create a group (receiver list).
- Add mailing
Create a mailing.
- Add Order Item
Add a new order item for subscriber.
- Add subscriber tags
Add tags to a receiver.
- Add/Update Subscriber
Adds a new subscriber in a selected list. Can be used to update an existing subscriber too.
- Delete group
Delete a group (receiver list).
- Delete subscriber
Delete a receiver from a group.
- Delete subscriber tags
Remove tags from a receiver.
- Find Subscriber
Search for subscribers in all lists in CleverReach. If found, the subscriber data will be returned along with the list id.
- Get group
Get a group (receiver list) by id.
- Get mailing
Get a mailing by id.
- Get subscriber
Get a receiver by id or email.
- List attributes
List attributes.
- List groups
List all groups (receiver lists).
- List mailings
List mailings.
- List subscribers
List receivers in a group.
- Unsubscribe Email
Unsubscribes an email address from a selected list.
- Update group
Update a group (receiver list).
- New Document
Triggers when a new Document is created.
- Add domain
Add a crawler domain to an Engine.
- Add engine
Create a new Engine (index).
- Create Document
Creates a new Document.
- Delete document
Delete a document by document_id from a document type.
- Delete domain
Remove a crawler domain from an Engine.
- Delete engine
Delete an Engine by id.
- Get document
Retrieve a single document by external_id from a document type.
- Get engine
Retrieve a single Engine by id or name.
- List documents
List documents within a document type/engine.
- List domains
List crawler domains configured on an Engine.
- List engines
List all Engines for the account.
- Recrawl domain
Trigger a recrawl of a domain's crawled content.
- Search documents
Perform full-text search over documents within an Engine.
- Update document
Update fields on an existing document.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from CleverReach
CleverReach to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
CleverReach to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
CleverReach to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
CleverReach to Google SheetsGoogle Sheets
CleverReach to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
CleverReach to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Swiftype
Questions
CleverReach and Swiftype, answered
What can start an automation from CleverReach?
Any of CleverReach's 3 triggers in the catalog, including New Campaign, New Subscriber and New Unsubscriber. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Swiftype when something happens in CleverReach?
Any of Swiftype's 14 actions, including Create Document, Update document, Add domain and Add engine. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Swiftype to CleverReach?
Yes. When something happens in Swiftype, your agent can act in CleverReach too. This page covers both directions: Swiftype's triggers and CleverReach's actions are listed here as well.
Do I have to build a connector for CleverReach or Swiftype?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.