Integration
Connect Mapulus and Zite
When New Location fires in Mapulus, your agent runs Create Record in Zite, or New Field in Zite 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 Zite 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 Mapulus and Zite can do together
From Mapulus to Zite
When New Location in Mapulus
then Create Record in Zite
When New Map in Mapulus
then Update Record in Zite
From Zite to Mapulus
When New Field in Zite
then Create Location in Mapulus
When New Record in Zite
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 Zite
Triggers and actions 11 triggers · 17 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
Deleted FieldTriggers when a field is deleted from a table.
Trigger
Deleted RecordTriggers when a record is deleted from a table.
Trigger
Deleted TableTriggers when a table is deleted from a base.
Trigger
New FieldTriggers when a new field is created in a table.
Trigger
New RecordTriggers when a new record is created in a table.
Trigger
New TableTriggers when a new table is created in a base.
Trigger
Updated FieldTriggers when a field is updated in a table.
Trigger
Updated RecordTriggers when an existing record is updated in a table.
Trigger
Updated TableTriggers when a table is updated in a base.
Action
Create FieldCreates a new field in a table.
Action
Create RecordCreates a new record in a table.
Action
Create TableCreates a new table in a base.
Action
Delete FieldDeletes a field from a table.
Action
Delete RecordDeletes a record from a table.
Action
Delete TableDeletes a table from a base.
Action
Find FieldFinds a field by name.
Action
Find RecordFinds a record by field value.
Action
Find TableFinds a table by name.
Action
Update FieldUpdates a field's name or settings.
Action
Update RecordUpdates an existing record in a table.
Action
Update TableUpdates a table's name or description.
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 Zite
HubSpot to ZiteHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to ZiteSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to ZiteSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to ZiteGoogle Sheets
Gmail to ZiteGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ZiteGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Mapulus and Zite, 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 Zite when something happens in Mapulus?
Any of Zite's 12 actions, including Create Field, Create Record, Create Table and Update Field. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Zite to Mapulus?
Yes. When something happens in Zite, your agent can act in Mapulus too. This page covers both directions: Zite's triggers and Mapulus's actions are listed here as well.
Do I have to build a connector for Mapulus or Zite?
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.