Integration
Connect Nimbata to Teambook
When New form submission fires in Nimbata, your agent runs Add Task in Teambook. 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 Teambook 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 Nimbata can start in Teambook
When New form submission in Nimbata
then Add Task in Teambook
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 Teambook
Triggers and actions 1 trigger · 44 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.
- Add Actual log
Creates one or more time-tracking actual logs in a batch.
- Add Booking
Creates one or more bookings in a batch.
- Add Client
Creates a client record.
- Add Task
Creates a task, optionally scoped to a project (omit project_id for account-wide task).
- Create Project
Create a Project inside Teambook
- Create User
Creates a teambook User
- Deactivate User
Deactivates a Teambook user so they can no longer be booked or sign in, without deleting their history.
- Delete Actual log
Deletes an actual log by id.
- Delete Booking
Removes a single booking from Teambook.
- Delete Project
Deletes a project by id.
- Delete Task
Deletes a task from the Teambook account.
- Delete User
Deletes a user from the Teambook account.
- Get Actual log
Retrieve a single Teambook actual log (time entry) by its id.
- Get Booking
Retrieve a single Teambook booking (a user's assignment to a project on a date for a duration) by its id.
- Get Client
Retrieves a single client by id.
- Get Project
Retrieves a single project by id.
- Get Task
Retrieves a single task by id.
- Get Team
Retrieve a single Teambook team by its id.
- Get User
Retrieve a single Teambook user by id.
- List Actual logs
Lists actual logs (timesheet entries), filterable by user_id, project_id, since, range.
- List Bookings
Lists bookings, optionally filtered by team, user, project and date window. Returns the first page of up to 100 bookings.
- List Clients
Returns every client in the Teambook account.
- List Project capacities
Lists project capacity entries (days reserved per project per month) entered on the Capacity by Project page.
- List Projects
Lists all projects in the Teambook account.
- List Tasks
Lists all tasks.
- List Teams
Lists all teams in the Teambook account.
- List User capacities
Lists monthly capacity-reservation rows per user, filterable by user_id and since (first day of month).
- List Users
Lists all users in the Teambook account.
- Update Actual log
Edits an actual log's project, user, date, duration, task, payroll_item, approved, or comment.
- Update Booking
Updates an existing Teambook booking; only the fields you fill in are changed.
- Update Client
Edits a client's name, phone_number, or email.
- Update Project
Edits a project's fields (name, code, active, color, kind, estimated, notes, client_id, manager_id, dates, custom_fields).
- Update Task
Edits a task's name or project_id.
- Update User
Edits a user's first_name, last_name, email, role, billable, time_zone, phone_number, language, or schedule.
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 Teambook
HubSpot to TeambookHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to TeambookGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to TeambookGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to TeambookGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Nimbata and Teambook, 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 Teambook when something happens in Nimbata?
Any of Teambook's 34 actions, including Create Project, Create User, Update Actual log and Update Booking. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Teambook to Nimbata?
Teambook has no triggers in the catalog today, so automations start in Nimbata. If you need the other direction, ask: your agent reads Teambook's API documentation and adds it.
Do I have to build a connector for Nimbata or Teambook?
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 Teambook 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.