Integration
Connect Particle and SQL Server
When New device event (instant) fires in Particle, your agent runs Add Row in SQL Server, or New or Updated Row in SQL Server 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 SQL Server 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 SQL Server can do together
From Particle to SQL Server
When New device event (instant) in Particle
then Add Row in SQL Server
From SQL Server 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 SQL Server
Triggers and actions 5 triggers · 12 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.
- New or Updated Row
Triggers when a new row is added or modified.
- New or Updated Row (Custom Query)
Fires for each new or changed row returned by a SELECT statement you write against the connected SQL Server database.
- New Row
Triggers when you add a new row.
- New Table
Fires when a new table appears in the connected SQL Server database.
- Add Row
Add one row to a table on the connected SQL Server database.
- Delete Row
Delete the rows in a table whose chosen column equals a value.
- Find Row
Find the first row in a table whose chosen column matches a value.
- Find Rows via Custom Query
Runs a SELECT statement you write against the connected SQL Server database and returns every row it matches.
- Find Row via Custom Query
Runs a SELECT statement you write against the connected SQL Server database and returns the first row it matches.
- Run Custom Statement
Runs a statement you write against the connected SQL Server database that changes data rather than returning rows, and reports how many rows it changed.
- Update Row
Change column values on every row of a table whose chosen column matches a value.
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 SQL Server
HubSpot to SQL ServerHubSpot is your all-in-one stop for all of your marketing software needs.
Mailchimp to SQL ServerMailchimp marketing automation and email platform.
QuickBooks Online to SQL ServerQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Pipedrive to SQL ServerPipedrive is a sales CRM and pipeline management tool.
Questions
Particle and SQL Server, 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 SQL Server when something happens in Particle?
Any of SQL Server's 7 actions, including Update Row, Add Row, Find Row and Find Rows via Custom Query. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from SQL Server to Particle?
Yes. When something happens in SQL Server, your agent can act in Particle too. This page covers both directions: SQL Server's triggers and Particle's actions are listed here as well.
Do I have to build a connector for Particle or SQL Server?
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 SQL Server 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.