Integration
Connect Particle and Pipefile
When New device event (instant) fires in Particle, your agent runs Create Contact in Pipefile, or File Request Created in Pipefile to Publish an event in Particle. 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 Particle and Pipefile 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 Particle and Pipefile can do together
From Particle to Pipefile
When New device event (instant) in Particle
then Create Contact in Pipefile
When New device event (instant) in Particle
then Update Contact in Pipefile
From Pipefile to Particle
When File Request Created in Pipefile
then Publish an event in Particle
When File Request Created in Pipefile
then Execute a logic function in Particle
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 Particle and Pipefile
Triggers and actions 2 triggers · 15 actions
Trigger
New device event (instant)Fires when a matching device event is published, delivered via a Particle webhook integration.
Action
Execute a logic functionRun a configured Particle Logic function and return its result.
Action
Get ledger instanceRetrieve the current data for a ledger instance (shared cloud/device key-value state).
Action
List devicesList all devices in your account or product fleet.
Action
Publish an eventPublish a custom event to the device cloud so other devices or integrations can subscribe to it.
Action
Set ledger instance dataUpdate the data stored in a ledger instance.
Trigger
File Request CreatedTriggers when a file request is created.
Action
Add File Request From TemplateCreate a new file request from an existing template for one recipient (name/email/phone), optionally on behalf of a team member via X-Pipefile-On-Behalf-Of.
Action
Create ContactAdd to contacts
Action
Delete ContactDelete a contact by id. Returns 204 No Content on success.
Action
Get ContactRetrieve one contact by id.
Action
Get File RequestRetrieve detailed information about one file request by id, including contents, items, files, and tracking events.
Action
List ContactsRetrieve a paginated list of contacts, filterable by name/email/phone partial match.
Action
List File Request TemplatesRetrieve the list of file request templates available for creating new file requests, with optional name search.
Action
Search File RequestsFinds all file requests matching this search query (contact name, email, tags, etc).
Action
Send RequestCreate and send a new request
Action
Update ContactUpdate name/email/phone of an existing contact by id.
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 Particle
Particle to ImprovMXAPI for free email forwarding service
Particle to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Particle to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Particle to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Particle to StripeStripe is a payment processing platform for online businesses.
Particle to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into Pipefile
HubSpot to PipefileHubSpot is your all-in-one stop for all of your marketing software needs.
Instagram to PipefileInstagram is a social media platform for sharing photos, videos, and stories.
CM.com to PipefileCM.com — create excellent conversational customer experiences and turn any conversation into a conversion.
EARLY to PipefileEARLY is a Time Tracking App: Effortless, Smart, and Secure.
Google Sheets to PipefileGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to PipefileGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Particle and Pipefile, answered
What can start an automation from Particle?
Any of Particle's 1 trigger in the catalog, including New device event (instant). Describe the moment in plain language and your agent picks the right one.
What can your agent do in Pipefile when something happens in Particle?
Any of Pipefile's 10 actions, including Create Contact, Send Request, Update Contact and Add File Request From Template. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Pipefile to Particle?
Yes. When something happens in Pipefile, your agent can act in Particle too. This page covers both directions: Pipefile's triggers and Particle's actions are listed here as well.
Do I have to build a connector for Particle or Pipefile?
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 Particle and Pipefile 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.