Integration
Connect Particle and Rendobar
When something happens in Particle or Rendobar, your agent does the next thing in the other. Describe it 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 Rendobar to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Rendobar can do together
From Particle to Rendobar
When New device event (instant) in Particle
then Add asset in Rendobar
From Rendobar to 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 Rendobar
Triggers and actions 2 triggers · 17 actions
- New device event (instant)
Fires when a matching device event is published, delivered via a Particle webhook integration.
- Execute a logic function
Run a configured Particle Logic function and return its result.
- Get ledger instance
Retrieve the current data for a ledger instance (shared cloud/device key-value state).
- List devices
List all devices in your account or product fleet.
- Publish an event
Publish a custom event to the device cloud so other devices or integrations can subscribe to it.
- Set ledger instance data
Update the data stored in a ledger instance.
- Job completed
Fires when a job finishes (success/failure). Backed by the vendor's webhook endpoint delivery mechanism, filtered to job-completion events.
- Add asset
Initialize an asset (media file) upload.
- Add job
Create a media processing job (transcode, caption, watermark, etc).
- Cancel job
Cancel a running job.
- Delete asset
Delete an asset by id.
- Get asset
Get details of an asset by id.
- Get job
Get details of a job by id.
- Get job logs
Get execution logs for a job.
- Get job output
Get the download URL/content for a completed job's output.
- List assets
List uploaded assets.
- List jobs
List jobs for the account.
- List job types
List available job types (transcode, caption, watermark, etc).
- List models
List available generation/processing models.
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 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
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.
Particle to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Rendobar
HubSpot to RendobarHubSpot is your all-in-one stop for all of your marketing software needs.
Gmail to RendobarGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to RendobarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to RendobarGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to RendobarMailchimp marketing automation and email platform.
Questions
Particle and Rendobar, 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 Rendobar when something happens in Particle?
Any of Rendobar's 12 actions, including Add asset, Add job, Get asset and Get job. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Rendobar to Particle?
Yes. When something happens in Rendobar, your agent can act in Particle too. This page covers both directions: Rendobar's triggers and Particle's actions are listed here as well.
Do I have to build a connector for Particle or Rendobar?
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.
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.