Integration
Connect Mapulus and Swiftype
When New Location fires in Mapulus, your agent runs Create Document in Swiftype, or New Document in Swiftype to Create Location in Mapulus. 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 Mapulus 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 Mapulus and Swiftype can do together
From Mapulus to Swiftype
When New Location in Mapulus
then Create Document in Swiftype
When New Map in Mapulus
then Update document in Swiftype
From Swiftype to Mapulus
When New Document in Swiftype
then Create Location in Mapulus
When New Document in Swiftype
then Update Location in Mapulus
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 Mapulus and Swiftype
Triggers and actions 3 triggers · 19 actions
Trigger
New LocationTriggers when a new location is added in Mapulus.
Trigger
New MapTriggers when a new map is created in Mapulus.
Action
Create LocationAdds a location pin to a layer on a Mapulus map, from an address or from coordinates.
Action
Delete LocationRemoves a location pin from a Mapulus map.
Action
Find LocationReturns Mapulus locations, optionally limited to one map or to the location with a given external ID.
Action
Find MapReturns the maps in your Mapulus account, so you can pick the one to add locations to.
Action
Update LocationUpdates a location pin in Mapulus. Only the fields you supply are changed.
Trigger
New DocumentTriggers when a new Document is created.
Action
Add domainAdd a crawler domain to an Engine.
Action
Add engineCreate a new Engine (index).
Action
Create DocumentCreates a new Document.
Action
Delete documentDelete a document by document_id from a document type.
Action
Delete domainRemove a crawler domain from an Engine.
Action
Delete engineDelete an Engine by id.
Action
Get documentRetrieve a single document by external_id from a document type.
Action
Get engineRetrieve a single Engine by id or name.
Action
List documentsList documents within a document type/engine.
Action
List domainsList crawler domains configured on an Engine.
Action
List enginesList all Engines for the account.
Action
Recrawl domainTrigger a recrawl of a domain's crawled content.
Action
Search documentsPerform full-text search over documents within an Engine.
Action
Update documentUpdate 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 Mapulus
Mapulus to StripeStripe is a payment processing platform for online businesses.
Mapulus to Zoho CampaignsZoho Campaigns lets you send email and social media campaigns to your subscribers.
Mapulus to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Mapulus to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Mapulus to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Mapulus to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
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.
Slack to SwiftypeSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to SwiftypeGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
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
Mapulus and Swiftype, answered
What can start an automation from Mapulus?
Any of Mapulus's 2 triggers in the catalog, including New Location and New Map. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Swiftype when something happens in Mapulus?
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 Mapulus?
Yes. When something happens in Swiftype, your agent can act in Mapulus too. This page covers both directions: Swiftype's triggers and Mapulus's actions are listed here as well.
Do I have to build a connector for Mapulus 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 Mapulus 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.