--- title: "Connect awork and Particle - APIANT.ai" description: "When \"New Client\" fires in awork, your agent runs \"Publish an event\" in Particle." canonical: "https://apiant.ai/connect/awork-to-particle" --- # Connect awork and Particle When **New Client** fires in [awork](https://apiant.ai/connections/awork), your agent runs **Publish an event** in [Particle](https://apiant.ai/connections/particle), or **New device event (instant)** in Particle to **Create Project Task** in awork. Describe the whole flow and it is built, tested on every scenario and kept running. awork **8** triggers awork **21** actions Particle **1** trigger Particle **5** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want awork and Particle 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 awork and Particle can do together ### From awork to Particle - When **New Client** in awork then **Publish an event** in Particle - When **New Project** in awork then **Execute a logic function** in Particle ### From Particle to awork - When **New device event (instant)** in Particle then **Create Project Task** in awork - When **New device event (instant)** in Particle then **Update Project Task** in awork 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 awork and Particle ## Triggers and actions 9 triggers · 26 actions - Trigger **New Client** Fires when a new company/client is created in awork. Poll/webhook on companies resource creation event. - Trigger **New Project** Triggers when a new project is created. - Trigger **New Task** Triggers when a new task is created. The trigger only fires for tasks with a project assigned, not for private tasks. - Trigger **New Time Entry** Triggers when a new time entry is created. - Trigger **Updated Client** Fires when an existing company/client is updated in awork. Poll/webhook on companies resource update event. - Trigger **Updated Project** Fires when a project is updated in the awork workspace. - Trigger **Updated Task** Triggers when a task is updated. The trigger only fires for tasks with a project assigned, not for private tasks. - Trigger **Updated Time Entry** Triggers when a time entry is updated. - Action **Create Client** Creates a client (company) in awork and returns the created company. - Action **Create Project** Creates a new project. - Action **Create Project Task** Creates a task in an awork project. - Action **Create Time Entry** Creates a time entry for a user, optionally against a project/task, using startDateUtc+duration or startDateUtc+endDateUtc. - Action **Delete Client** Deletes a client (company) in awork, optionally moving, detaching or deleting its linked projects and tasks. - Action **Delete Project** Deletes an awork project and its tasks, optionally deleting its time entries too. - Action **Delete Project Task** Deletes an awork task by id. - Action **Delete Time Entry** Deletes a time entry in awork. - Action **Find Project Tasks by criteria** Returns up to 100 tasks of a project that match the specified filter criteria. - Action **Find Time Entries by criteria** Returns up to 100 time entries in the workspace that match the specified filter criteria. - Action **Get Client by ID** Finds a client by id - Action **Get Project by ID** Finds a project by id - Action **Get Task by ID** Returns a single awork task (project or private task) by its id, including status, assignees, project, tags, lists and custom field values. - Action **Get Time Entry** Returns a single awork time entry by its id, including its task, project, user, type of work and breaks. - Action **Search Clients** Returns up to 100 clients (companies) whose name contains the specified text. - Action **Search Projects** Returns up to 100 projects whose name contains the specified text, optionally narrowed by an additional filter. - Action **Search Users by Email** Returns the awork users whose contact information includes the specified email address. - Action **Update Client** Updates an existing client (company) by ID. Fields left blank keep their current values. - Action **Update Project** Updates fields (name, status, workflow, etc) on an existing awork project. - Action **Update Project Task** Updates fields (name, status, assignee, due date, etc) on an existing awork task. - Action **Update Time Entry** Updates an existing awork time entry: its times or duration, type of work, project, task, note and billing flags. - 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. ## Each app on its own - [ **awork** Intelligent projects, tasks and time tracking for your project business.](https://apiant.ai/connections/awork) - [ **Particle** Particle is an Internet of Things (IoT) device platform that enables businesses to easily add the power of...](https://apiant.ai/connections/particle) Reviews ## What our customers say ## More from awork - [ **awork to agilite** Low-code platform providing BPM, business rules, roles, and API-key managed services for workflow automation.](https://apiant.ai/connect/awork-to-agilite) - [ **awork to ShareFile** Securely send, store, and share files – plus discover document workflows designed to improve your client...](https://apiant.ai/connect/awork-to-sharefile) - [ **awork to Vouchery.io** Vouchery is an all-in-one promotional suite to help you orchestrate & deliver the right incentive at every...](https://apiant.ai/connect/awork-to-vouchery-io) - [ **awork to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/awork-to-hubspot) - [ **awork to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/awork-to-salesforce) - [ **awork to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/awork-to-slack) ## More into Particle - [ **NetHunt CRM to Particle** NetHunt CRM ties to Gmail and other Google Workspace apps you work in, automates data flow, and makes...](https://apiant.ai/connect/nethunt-crm-to-particle) - [ **HubSpot to Particle** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-particle) - [ **Gmail to Particle** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-particle) - [ **Google Calendar to Particle** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-particle) - [ **Google Drive to Particle** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-particle) - [ **Mailchimp to Particle** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-particle) Questions ## awork and Particle, answered ### ### What can start an automation from awork? Any of awork's 8 triggers in the catalog, including New Client, New Project, New Task and New Time Entry. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Particle when something happens in awork? 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 awork? Yes. When something happens in Particle, your agent can act in awork too. This page covers both directions: Particle's triggers and awork's actions are listed here as well. ### ### Do I have to build a connector for awork 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. ### ### Can my AI client use awork and Particle 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.