Integration
Connect Erpnext and Particle
When something happens in Erpnext or Particle, 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 Erpnext and Particle 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 Erpnext and Particle can do together
From Erpnext to Particle
When New Customer in Erpnext
then Execute a logic function in Particle
From Particle to Erpnext
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 Erpnext and Particle
Triggers and actions 3 triggers · 35 actions
- New Customer
Fires when a new customer is created.
- New Sales Invoice
Fires when a new sales invoice is created.
- Add Contact
Create a new contact.
- Add Customer
Create a new customer record.
- Add Item
Create a new item (product/service) record.
- Add Lead
Create a new lead.
- Add Sales Invoice
Create a new sales invoice.
- Add Sales Order
Create a new sales order.
- Delete Contact
Delete a contact record.
- Delete Customer
Delete a customer record.
- Delete Item
Delete an item record.
- Delete Lead
Delete a lead record.
- Delete Sales Invoice
Delete a sales invoice record.
- Delete Sales Order
Delete a sales order record.
- Get Contact
Retrieve a single contact by name/id.
- Get Customer
Retrieve a single customer by name/id.
- Get Item
Retrieve a single item by name/id.
- Get Lead
Retrieve a single lead by name/id.
- Get Sales Invoice
Retrieve a single sales invoice by name/id.
- Get Sales Order
Retrieve a single sales order by name/id.
- List Contacts
List contact records with optional filters.
- List Customers
List customer records with optional filters.
- List Items
List item records with optional filters.
- List Leads
List lead records with optional filters.
- List Sales Invoices
List sales invoice records with optional filters.
- List Sales Orders
List sales order records with optional filters.
- Update Contact
Update fields on an existing contact.
- Update Customer
Update fields on an existing customer.
- Update Item
Update fields on an existing item.
- Update Lead
Update fields on an existing lead.
- Update Sales Invoice
Update fields on an existing sales invoice.
- Update Sales Order
Update fields on an existing sales order.
- 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.
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 Erpnext
Erpnext to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Erpnext to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Erpnext to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Erpnext to Google SheetsGoogle Sheets
Erpnext to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Erpnext to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Particle
Google Drive to ParticleGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to ParticleMailchimp marketing automation and email platform.
ActiveCampaign to ParticleActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
Erpnext and Particle, answered
What can start an automation from Erpnext?
Any of Erpnext's 2 triggers in the catalog, including New Customer and New Sales Invoice. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Particle when something happens in Erpnext?
Any of Particle's 5 actions, including Execute a logic function, Get ledger instance, List devices and Publish an event. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Particle to Erpnext?
Yes. When something happens in Particle, your agent can act in Erpnext too. This page covers both directions: Particle's triggers and Erpnext's actions are listed here as well.
Do I have to build a connector for Erpnext or Particle?
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.