Integration
Connect Nimbata and Terros
When New form submission fires in Nimbata, your agent runs Create User in Terros, or New Account in Terros to Get lead in Nimbata. 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 Nimbata and Terros 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 Nimbata and Terros can do together
From Nimbata to Terros
When New form submission in Nimbata
then Create User in Terros
From Terros to Nimbata
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 Nimbata and Terros
Triggers and actions 9 triggers · 28 actions
- New form submission
Triggers when a new form submission is received in a Nimbata project.
- Add tag
Creates a new tag in a tag category of a Nimbata project, ready to be applied to calls and form submissions.
- Add tags to call
Adds one or more tags to a call and keeps the tags it already has. Returns the call's full list of tag IDs after the change.
- Get call
Returns an inbound call's details, including its attribution, call-flow information and custom field values.
- Get lead
Returns one lead with its phone numbers, emails, and first and last interaction details. If the lead was merged into another, returns the surviving lead.
- Get tracking number
Returns one tracking number from a project, looked up by its ID or phone number, including its status, line type, country, call flow and tracking source.
- List calls
Returns the inbound and outbound calls of a project, newest first, optionally narrowed by date range, caller, tracking number, outcome or campaign.
- List form submissions
Returns the form submissions recorded in a Nimbata project, optionally narrowed by form, date range, attribution, device, tag or value.
- List leads
Returns the identified leads in a Nimbata project, most recent interaction first, optionally narrowed to one phone number or email address.
- List SMS messages
Returns a project's SMS messages, newest first, optionally filtered by date range, direction, status or phone number.
- List tracking numbers
Returns the tracking numbers in a Nimbata project, optionally narrowed by a name or phone number search.
- List Calendar Events
Triggers when a new calendar event appears in Terros.
- List Status Ids
Triggers when a new disposition (account status) is added in Terros.
- List Tasks
Triggers when a new task appears in Terros.
- List Workflow Action IDs
Triggers when a new action is added to a Terros workflow.
- List Workflow IDs
Triggers when a new workflow is added in Terros.
- List Workflow Stage IDs
Triggers when a new stage is added to a Terros workflow.
- New Account
Triggers when a new account is added in Terros.
- New User
Triggers when a new user is added to your Terros company.
- Add meeting
Creates a recurring team meeting in Terros with a schedule, reminders and optional check-in rules.
- Create/Update Account
Creates a Terros account, or updates it when the account ID is given.
- Create User
Adds a user to your Terros company.
- Delete Account
Deletes an account (a homeowner or lead record) from Terros by its account ID.
- Delete Calendar Event
Deletes a calendar event.
- Delete meeting
Archives a meeting in Terros, or permanently deletes it when Archive is set to false.
- Delete task
Removes one or more Terros tasks, archiving them by default or deleting them permanently.
- Delete User
Removes a user from your Terros company.
- Find Account
Finds a Terros account by account ID, external lead ID or source ID.
- Find User
Finds users whose name or email matches the search text.
- Get task
Returns a single Terros task by its ID, including its subject, status, owner and criteria.
- List Accounts
Returns accounts, optionally filtered by user, workflow or search text.
- List Available Closers
Lists closers and their open appointment times for a team or user.
- List Users
Returns the users in your Terros company, optionally limited to one team.
- List Workflow IDs
Returns the workflows you can see, with their IDs.
- Make Report
Runs a KPI report for the chosen KPIs, grouped by user, team or another dimension.
- Update meeting
Updates a Terros meeting, replacing its team, name, recurring schedule, reminders, check-in options, location and meeting link.
- Update User
Updates a Terros user's name, email, phone or time zone.
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 Nimbata
Nimbata to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Nimbata to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Nimbata to StripeStripe is a payment processing platform for online businesses.
Nimbata to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Nimbata to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Nimbata to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into Terros
HubSpot to TerrosHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to TerrosGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to TerrosGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to TerrosGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Nimbata and Terros, answered
What can start an automation from Nimbata?
Any of Nimbata's 1 trigger in the catalog, including New form submission. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Terros when something happens in Nimbata?
Any of Terros's 18 actions, including Create/Update Account, Create User, Update meeting and Update User. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Terros to Nimbata?
Yes. When something happens in Terros, your agent can act in Nimbata too. This page covers both directions: Terros's triggers and Nimbata's actions are listed here as well.
Do I have to build a connector for Nimbata or Terros?
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 Nimbata and Terros 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.