--- title: "Connect awork to Fergus - APIANT.ai" description: "When \"New Client\" fires in awork, your agent runs \"Add Contact\" in Fergus. Describe the whole flow and it is built, tested on every scenario and kept running." canonical: "https://apiant.ai/connect/awork-to-fergus" --- # Connect awork to Fergus When **New Client** fires in [awork](https://apiant.ai/connections/awork), your agent runs **Add Contact** in [Fergus](https://apiant.ai/connections/fergus). Describe the whole flow and it is built, tested on every scenario and kept running. awork **8** triggers awork **21** actions Fergus **31** 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 Fergus 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 can start in Fergus - When **New Client** in awork then **Add Contact** in Fergus - When **New Project** in awork then **Add Task** in Fergus 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 Fergus ## Triggers and actions 8 triggers · 52 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. - Action **Add Calendar Event** Creates a new calendar event/booking. - Action **Add Contact** Creates a new contact. - Action **Add Note** Creates a new note against a record. - Action **Add Quote** Creates a new draft quote on a Fergus job. Supported for jobs whose job type is Quote or Estimate. - Action **Add Task** Creates a new task in Fergus, optionally linked to a job and assigned to employees. - Action **Archive Site** Archives a site in Fergus. The site can later be restored. - Action **Create Customer** Creates a new customer. - Action **Create Job** Creates a job in Fergus — an active job, a draft job, or a variation of an existing job. - Action **Create Site** Creates a new site. - Action **Delete Customer** Deletes a Fergus customer by ID. - Action **Edit Draft Job** Updates a draft job in Fergus. Only draft jobs can be edited; leave a field blank to keep its current value. - Action **Finalize Draft Job** Finalises a draft job in Fergus, turning it into an active job. - Action **Find All Quotes** Returns up to 100 quotes from across all jobs that match the specified status and date criteria. - Action **Find Customer** Returns the customers whose name, or main or billing contact's name, email or phone, contains the search text. - Action **Find Site** Finds sites by name, city, postal code, or free-text search. Returns the first page of matches (up to 10). - Action **Get Calendar Event** Returns a single Fergus calendar event by its ID, including title, start/end times, event type, assigned user, linked job/job phase and recurrence details. - Action **Get Contact** Returns a single Fergus contact (customer or site contact) by its ID, including name, position, company and contact items. - Action **Get Customer by ID** Returns a Fergus customer by its ID. - Action **Get Customer Invoice** Retrieves a customer invoice by ID. - Action **Get Job by ID** Retrieves a specific job using its unique ID. - Action **Get Quotes for Job** Returns all quotes for a Fergus job, optionally filtered by status. - Action **Get Site by ID** Retrieves a specific site using its unique ID. - Action **List Contacts** Lists contacts, with optional filtering. - Action **List Customer Invoices** Lists customer invoices, with optional filtering. - Action **List Notes** Returns the notes (with their replies) attached to a Fergus record. - Action **List Tasks** Lists the company's tasks, optionally filtered by status, assigned employee, job, due date range or overdue state. - Action **Update Contact** Updates an existing customer contact or site contact in Fergus. - Action **Update Customer** Updates an existing customer's details. - Action **Update Quote** Updates a draft quote on a Quote or Estimate job in Fergus: title, description and its sections with line items. - Action **Update Site** Updates an existing site's details. - Action **Update Task** Updates a task's description, due date, or assigned employees in Fergus. The job a task is linked to cannot be changed. ## Each app on its own - [ **awork** Intelligent projects, tasks and time tracking for your project business.](https://apiant.ai/connections/awork) - [ **Fergus** Fergus is a job management software for plumbers, electricians and other trades.](https://apiant.ai/connections/fergus) 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 Fergus - [ **Outlook to Fergus** Outlook is Microsoft's email and calendaring platform integrating contacts and scheduling, enabling users to...](https://apiant.ai/connect/outlook-to-fergus) - [ **HubSpot to Fergus** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-fergus) - [ **Salesforce to Fergus** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-fergus) - [ **Slack to Fergus** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-fergus) - [ **Google Sheets to Fergus** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-fergus) - [ **Gmail to Fergus** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-fergus) Questions ## awork and Fergus, 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 Fergus when something happens in awork? Any of Fergus's 31 actions, including Create Customer, Create Job, Create Site and Update Contact. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Fergus to awork? Fergus has no triggers in the catalog today, so automations start in awork. If you need the other direction, ask: your agent reads Fergus's API documentation and adds it. ### ### Do I have to build a connector for awork or Fergus? 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 Fergus 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.