--- title: "Connect awork and Cursor - APIANT.ai" description: "When \"New Client\" fires in awork, your agent runs \"Add Followup Instruction to Agent\" in Cursor." canonical: "https://apiant.ai/connect/awork-to-cursor" --- # Connect awork and Cursor When **New Client** fires in [awork](https://apiant.ai/connections/awork), your agent runs **Add Followup Instruction to Agent** in [Cursor](https://apiant.ai/connections/cursor), or **Agent Pull Request Created** in Cursor 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 Cursor **3** triggers Cursor **11** 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 Cursor 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 Cursor can do together ### From awork to Cursor - When **New Client** in awork then **Add Followup Instruction to Agent** in Cursor - When **New Project** in awork then **Launch Agent** in Cursor ### From Cursor to awork - When **Agent Pull Request Created** in Cursor then **Create Project Task** in awork - When **New Agent** in Cursor 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 Cursor ## Triggers and actions 11 triggers ยท 32 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 **Agent Pull Request Created** Triggers when the selected Cursor cloud agent opens a new GitHub pull request. - Trigger **Agent Status Equals** Triggers when a run on the chosen Cursor agent reaches the status you select, such as Finished or Error. - Trigger **New Agent** Triggered when a new Cursor cloud agent is created. - Action **Add Followup Instruction to Agent** Sends a follow-up instruction to an existing Cursor cloud agent, either starting a new run or steering the run in progress. Returns the new run or how the steer was delivered. - Action **Cancel run** Cancels the active run of a Cursor cloud agent. The run ends in the Cancelled state; start a new run to continue the conversation. - Action **Delete Agent** Permanently deletes a Cursor cloud agent. This cannot be undone. Returns the ID of the deleted agent. - Action **Find Agent Status** Looks up a Cursor cloud agent by its ID and returns its status, name, repositories, latest run and link. - Action **Get run** Returns the status, timestamps, duration, final reply and pushed branches for one run of a Cursor cloud agent. - Action **Launch Agent** Creates a Cursor cloud agent and immediately starts its first run on the task you describe. Returns the new agent and its run. - Action **List agents** Returns the Cursor cloud agents for the connected user, newest first, optionally filtered by pull request URL. - Action **List artifacts** Returns the files a Cursor cloud agent has produced, with each file's path, size and last modified time. Returns at most 100 artifacts. - Action **List models** Returns the recommended Cursor models you can choose from when creating an agent, including their names, aliases, parameters and variants. - Action **List repositories** Returns the GitHub repositories the connected Cursor user can access through Cursor's GitHub App installation. - Action **List runs** Returns the runs of a Cursor cloud agent, newest first, including each run's status, duration, and final reply. ## Each app on its own - [ **awork** Intelligent projects, tasks and time tracking for your project business.](https://apiant.ai/connections/awork) - [ **Cursor** Cursor is an AI-powered code editor that understands your codebase, supports natural-language coding...](https://apiant.ai/connections/cursor) 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 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) - [ **awork to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/awork-to-google-sheets) ## More into Cursor - [ **ActiveCampaign to Cursor** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-cursor) - [ **Airtable to Cursor** Organize anything with Airtable, a modern database created for everyone.](https://apiant.ai/connect/airtable-to-cursor) - [ **Asana to Cursor** Asana is a collaborative information manager for workspace.](https://apiant.ai/connect/asana-to-cursor) - [ **ClickUp to Cursor** ClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.](https://apiant.ai/connect/clickup-to-cursor) - [ **Brevo to Cursor** Brevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...](https://apiant.ai/connect/brevo-to-cursor) - [ **Calendly to Cursor** Calendly is a scheduling automation platform for eliminating the back-and-forth emails to find the perfect...](https://apiant.ai/connect/calendly-to-cursor) Questions ## awork and Cursor, 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 Cursor when something happens in awork? Any of Cursor's 11 actions, including Add Followup Instruction to Agent, Find Agent Status, Get run and Launch Agent. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Cursor to awork? Yes. When something happens in Cursor, your agent can act in awork too. This page covers both directions: Cursor's triggers and awork's actions are listed here as well. ### ### Do I have to build a connector for awork or Cursor? 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 Cursor 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.