Integration
Connect Particle and Ticket Generator
When New device event (instant) fires in Particle, your agent runs Create Event in Ticket Generator, or New Event Created in Ticket Generator 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 Ticket Generator 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 Particle and Ticket Generator can do together
From Particle to Ticket Generator
When New device event (instant) in Particle
then Create Event in Ticket Generator
When New device event (instant) in Particle
then List Events in Ticket Generator
From Ticket Generator to Particle
When New Event Created in Ticket Generator
then Publish an event in Particle
When Event Ended in Ticket Generator
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 Ticket Generator
Triggers and actions 3 triggers · 8 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
Event EndedTriggers when an event has ended.
Trigger
New Event CreatedTriggers when a new event is created in Ticket Generator.
Action
Create EventCreates a new event with a name, start date and optional venue, end date, capacity and description.
Action
Get Account AnalyticsReturns totals and attendance across all events in the account, optionally grouped by week or month.
Action
List EventsReturns events in the account, optionally filtered by status or date range.
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 Ticket Generator
HubSpot to Ticket GeneratorHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Ticket GeneratorSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Ticket GeneratorSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Ticket GeneratorGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Ticket GeneratorGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Ticket GeneratorGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Particle and Ticket Generator, 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 Ticket Generator when something happens in Particle?
Any of Ticket Generator's 3 actions, including Create Event, Get Account Analytics and List Events. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Ticket Generator to Particle?
Yes. When something happens in Ticket Generator, your agent can act in Particle too. This page covers both directions: Ticket Generator's triggers and Particle's actions are listed here as well.
Do I have to build a connector for Particle or Ticket Generator?
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 Ticket Generator 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.