---
title: "Connect Nimbata and Particle - APIANT.ai"
description: "When \"New form submission\" fires in Nimbata, your agent runs \"Publish an event\" in Particle."
canonical: "https://apiant.ai/connect/nimbata-to-particle"
---

# Connect Nimbata and Particle

When **New form submission** fires in [Nimbata](https://apiant.ai/connections/nimbata), your agent runs **Publish an event** in [Particle](https://apiant.ai/connections/particle), or **New device event (instant)** in Particle to **Get lead** in Nimbata. Describe the whole flow and it is built, tested on every scenario and kept running.

Nimbata **1** trigger Nimbata **10** actions Particle **1** trigger Particle **5** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want Nimbata and Particle to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One 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.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

Example flows

## What Nimbata and Particle can do together

### From Nimbata to Particle

- When **New form submission** in Nimbata then **Publish an event** in Particle
- When **New form submission** in Nimbata then **Execute a logic function** in Particle

### From Particle to Nimbata

- When **New device event (instant)** in Particle then **Get lead** in Nimbata
- When **New device event (instant)** in Particle then **List leads** in 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 Particle

## Triggers and actions 2 triggers · 15 actions

- Trigger

**New form submission**

Triggers when a new form submission is received in a Nimbata project.

- Action

**Add tag**

Creates a new tag in a tag category of a Nimbata project, ready to be applied to calls and form submissions.

- Action

**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.

- Action

**Get call**

Returns an inbound call's details, including its attribution, call-flow information and custom field values.

- Action

**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.

- Action

**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.

- Action

**List calls**

Returns the inbound and outbound calls of a project, newest first, optionally narrowed by date range, caller, tracking number, outcome or campaign.

- Action

**List form submissions**

Returns the form submissions recorded in a Nimbata project, optionally narrowed by form, date range, attribution, device, tag or value.

- Action

**List leads**

Returns the identified leads in a Nimbata project, most recent interaction first, optionally narrowed to one phone number or email address.

- Action

**List SMS messages**

Returns a project's SMS messages, newest first, optionally filtered by date range, direction, status or phone number.

- Action

**List tracking numbers**

Returns the tracking numbers in a Nimbata project, optionally narrowed by a name or phone number search.

- Trigger

**New device event (instant)**

Fires when a matching device event is published, delivered via a Particle webhook integration.

- Action

**Execute a logic function**

Run a configured Particle Logic function and return its result.

- Action

**Get ledger instance**

Retrieve the current data for a ledger instance (shared cloud/device key-value state).

- Action

**List devices**

List all devices in your account or product fleet.

- Action

**Publish an event**

Publish a custom event to the device cloud so other devices or integrations can subscribe to it.

- Action

**Set ledger instance data**

Update the data stored in a ledger instance.

## Each app on its own

- [ **Nimbata** Nimbata is a call tracking platform that lets you attribute phone calls back to keyword searches, web pages...](https://apiant.ai/connections/nimbata)
- [ **Particle** Particle is an Internet of Things (IoT) device platform that enables businesses to easily add the power of...](https://apiant.ai/connections/particle)

Reviews

## What our customers say

## More from Nimbata

- [ **Nimbata to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/nimbata-to-salesforce)
- [ **Nimbata to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/nimbata-to-slack)
- [ **Nimbata to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/nimbata-to-stripe)
- [ **Nimbata to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/nimbata-to-shopify)
- [ **Nimbata to QuickBooks Online** QuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...](https://apiant.ai/connect/nimbata-to-quickbooks-online)
- [ **Nimbata to Pipedrive** Pipedrive is a sales CRM and pipeline management tool.](https://apiant.ai/connect/nimbata-to-pipedrive)

## More into Particle

- [ **NetHunt CRM to Particle** NetHunt CRM ties to Gmail and other Google Workspace apps you work in, automates data flow, and makes...](https://apiant.ai/connect/nethunt-crm-to-particle)
- [ **HubSpot to Particle** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-particle)
- [ **Gmail to Particle** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-particle)
- [ **Google Calendar to Particle** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-particle)
- [ **Google Drive to Particle** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-particle)
- [ **Mailchimp to Particle** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-particle)

Questions

## Nimbata and Particle, 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 Particle when something happens in Nimbata?

Any of Particle's 5 actions, including Execute a logic function, Get ledger instance, List devices and Publish an event. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Particle to Nimbata?

Yes. When something happens in Particle, your agent can act in Nimbata too. This page covers both directions: Particle's triggers and Nimbata's actions are listed here as well.

###

### Do I have to build a connector for Nimbata or Particle?

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 Particle 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.
