Integration
Connect Sender and Swiftype
When New Group fires in Sender, your agent runs Create Document in Swiftype, or New Document in Swiftype to Unsubscribe Email in Sender. Describe the whole flow 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 Sender and Swiftype to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any 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 Sender and Swiftype can do together
From Sender to Swiftype
When New Group in Sender
then Create Document in Swiftype
From Swiftype to Sender
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 Sender and Swiftype
Triggers and actions 5 triggers · 24 actions
- New Group
Triggers when a new group is created.
- New Subscriber
Triggers when a new subscriber is added.
- New Unsubscriber From Group
Triggers when a subscriber is removed from a group.
- Updated Subscriber
Triggers when a subscriber is updated.
- Add group
Create a new subscriber group.
- Add Subscriber to Group
Adds a subscriber to a group.
- Add / Update Subscriber
Adds a new subscriber. If subscriber with the same email exists, updates the subscriber's data.
- Create Campaign
Creates a draft campaign
- Get campaign
Retrieve details of a single campaign by campaign id.
- Get subscriber
Retrieve a single subscriber's data by email or subscriber id.
- List groups
List all subscriber groups on the account.
- List subscribers
List all subscribers on the account, paginated.
- Remove Subscriber From Group
Removes a subscriber from a group.
- Unsubscribe Email
Unsubscribes an email address.
- 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 Sender
Sender to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Sender to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Sender to StripeStripe is a payment processing platform for online businesses.
Sender to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Sender to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Sender to TwilioCloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...
More into Swiftype
HubSpot to SwiftypeHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SwiftypeSalesforce is a leading enterprise customer relationship management (CRM) platform.
Gmail to SwiftypeGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SwiftypeGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Sender and Swiftype, answered
What can start an automation from Sender?
Any of Sender's 4 triggers in the catalog, including New Group, New Subscriber, New Unsubscriber From Group and Updated Subscriber. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Swiftype when something happens in Sender?
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 Sender?
Yes. When something happens in Swiftype, your agent can act in Sender too. This page covers both directions: Swiftype's triggers and Sender's actions are listed here as well.
Do I have to build a connector for Sender 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.
Can my AI client use Sender and Swiftype without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
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.