---
title: "Connect Particle to Svix - APIANT.ai"
description: "When \"New device event (instant)\" fires in Particle, your agent runs \"Add event type\" in Svix."
canonical: "https://apiant.ai/connect/particle-to-svix"
---

# Connect Particle to Svix

When **New device event (instant)** fires in [Particle](https://apiant.ai/connections/particle), your agent runs **Add event type** in [Svix](https://apiant.ai/connections/svix). Describe the whole flow and it is built, tested on every scenario and kept running.

Particle **1** trigger Particle **5** actions Svix **19** actions

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

## What do you want Particle and Svix 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 Particle can start in Svix

- When **New device event (instant)** in Particle then **Add event type** in Svix
- When **New device event (instant)** in Particle then **Add message** in Svix

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 Svix

## Triggers and actions 1 trigger · 24 actions

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

- Action

**Add application**

Creates a new Svix application, the destination your webhook messages are sent to (usually one per customer).

- Action

**Add endpoint**

Creates a new webhook endpoint (a destination URL) on a Svix application.

- Action

**Add event type**

Creates a new event type in Svix, or unarchives an existing one with the same name.

- Action

**Add message**

Creates a new message (webhook) in a Svix application and dispatches it to all of the application's subscribed endpoints.

- Action

**Delete application**

Deletes a Svix application and its endpoints.

- Action

**Delete endpoint**

Deletes an endpoint from a Svix application so it no longer receives messages.

- Action

**Get application**

Returns a Svix application by its id or your own UID.

- Action

**Get endpoint**

Returns a webhook endpoint of a Svix application, including its URL, subscribed event types, channels and status.

- Action

**Get endpoint secret**

Returns the signing secret of a webhook endpoint, used to verify that incoming webhooks were sent by Svix.

- Action

**Get message**

Returns a single message (webhook) sent to an application, by its message ID or event ID, including its payload.

- Action

**List applications**

Returns the applications in your Svix organization, optionally excluding those without active endpoints.

- Action

**List endpoints**

Returns the endpoints (webhook destination URLs) configured on a Svix application.

- Action

**List event types**

Returns the event types defined in your Svix environment.

- Action

**List message attempts**

Returns the delivery attempts made for a message, with each attempt's endpoint, URL, status and response.

- Action

**List messages**

Returns the messages (webhooks) sent to a Svix application, optionally filtered by channel, tag, event type or date range.

- Action

**Resend message**

Resends an existing webhook message to one of the application's endpoints.

- Action

**Rotate endpoint secret**

Rotates an endpoint's webhook signing secret. The previous secret stays valid for a grace period (24 hours by default).

- Action

**Update application**

Updates an existing Svix application's name, UID, throttle rate or metadata. Only the values you fill in are changed.

- Action

**Update endpoint**

Updates selected settings of a webhook endpoint in a Svix application, such as its URL, description, subscribed event types or channels. Fields left blank are unchanged.

## Each app on its own

- [ **Particle** Particle is an Internet of Things (IoT) device platform that enables businesses to easily add the power of...](https://apiant.ai/connections/particle)
- [ **Svix** Webhooks-as-a-service platform for sending, retrying, and securing outbound webhook event delivery.](https://apiant.ai/connections/svix)

Reviews

## What our customers say

## More from Particle

- [ **Particle to ImprovMX** API for free email forwarding service](https://apiant.ai/connect/particle-to-improvmx)
- [ **Particle to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/particle-to-salesforce)
- [ **Particle to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/particle-to-slack)
- [ **Particle to Google Sheets** Google Sheets](https://apiant.ai/connect/particle-to-google-sheets)
- [ **Particle to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/particle-to-stripe)
- [ **Particle to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/particle-to-shopify)

## More into Svix

- [ **HubSpot to Svix** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-svix)
- [ **Salesforce to Svix** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-svix)
- [ **Slack to Svix** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-svix)
- [ **Google Sheets to Svix** Google Sheets](https://apiant.ai/connect/google-sheets-to-svix)
- [ **Gmail to Svix** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-svix)
- [ **Google Calendar to Svix** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-svix)

Questions

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

Any of Svix's 19 actions, including Update application, Update endpoint, Add application and Add endpoint. Your agent maps the data both ways and tests every scenario before it ships.

###

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

Svix has no triggers in the catalog today, so automations start in Particle. If you need the other direction, ask: your agent reads Svix's API documentation and adds it.

###

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

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