Integration
Connect Groove to Fergus
When Customer Added fires in Groove, your agent runs Create Customer in Fergus. Describe the whole flow 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 Groove and Fergus to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.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 Groove can start in Fergus
When Customer Added in Groove
then Create Customer 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 Groove and Fergus
Triggers and actions 9 triggers · 46 actions
- Agent Replied
Triggers when an agent replies to a ticket.
- Customer Added
Triggers when a customer is created.
- Customer Replied
Triggers when a customer replies to a ticket.
- Note Added
Triggers when a note is added to a ticket.
- Ticket Assigned
Triggers when a ticket is assigned.
- Ticket Closed
Triggers when a ticket is closed.
- Ticket Opened
Triggers when a ticket is opened.
- Ticket Started
Triggers when a new ticket is created.
- Ticket Tagged
Triggers when a ticket is tagged.
- Add label to ticket
Adds one or more labels to a Groove ticket, keeping its existing labels, and returns the updated ticket.
- Add message
Adds a new message (reply or private note) to an existing Groove ticket.
- Add Note
Adds a private note to a Groove ticket, visible only to agents.
- Change Assigned Agent
Assigns a Groove ticket to a different agent, identified by the agent's email address.
- Change Ticket Mailbox
Moves a ticket into a different mailbox.
- Change Ticket State
Changes the state of a Groove ticket (unread, opened, pending, closed or spam).
- Close Ticket
Closes a Groove ticket by setting its state to closed.
- Create New Ticket
Creates a new ticket in Groove from a customer or agent, with its first message.
- Get customer
Returns one Groove customer, looked up by email address, including their contact details and custom attributes.
- Get ticket
Returns a single Groove ticket by its ticket number.
- List agents
Returns the agents on your Groove account, optionally limited to one group.
- List mailboxes
Returns all mailboxes in the Groove account, with each mailbox's name and email address.
- List messages
Returns the messages and notes on a Groove ticket.
- Reopen Ticket
Reopens a Groove ticket by setting its state to opened.
- Update customer
Updates a customer's profile details, such as name, company, title and contact info, identified by their email address.
- Add Calendar Event
Creates a new calendar event/booking.
- Add Contact
Creates a new contact.
- Add Note
Creates a new note against a record.
- Add Quote
Creates a new draft quote on a Fergus job. Supported for jobs whose job type is Quote or Estimate.
- Add Task
Creates a new task in Fergus, optionally linked to a job and assigned to employees.
- Archive Site
Archives a site in Fergus. The site can later be restored.
- Create Customer
Creates a new customer.
- Create Job
Creates a job in Fergus — an active job, a draft job, or a variation of an existing job.
- Create Site
Creates a new site.
- Delete Customer
Deletes a Fergus customer by ID.
- Edit Draft Job
Updates a draft job in Fergus. Only draft jobs can be edited; leave a field blank to keep its current value.
- Finalize Draft Job
Finalises a draft job in Fergus, turning it into an active job.
- Find All Quotes
Returns up to 100 quotes from across all jobs that match the specified status and date criteria.
- Find Customer
Returns the customers whose name, or main or billing contact's name, email or phone, contains the search text.
- Find Site
Finds sites by name, city, postal code, or free-text search. Returns the first page of matches (up to 10).
- 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.
- Get Contact
Returns a single Fergus contact (customer or site contact) by its ID, including name, position, company and contact items.
- Get Customer by ID
Returns a Fergus customer by its ID.
- Get Customer Invoice
Retrieves a customer invoice by ID.
- Get Job by ID
Retrieves a specific job using its unique ID.
- Get Quotes for Job
Returns all quotes for a Fergus job, optionally filtered by status.
- Get Site by ID
Retrieves a specific site using its unique ID.
- List Contacts
Lists contacts, with optional filtering.
- List Customer Invoices
Lists customer invoices, with optional filtering.
- List Notes
Returns the notes (with their replies) attached to a Fergus record.
- List Tasks
Lists the company's tasks, optionally filtered by status, assigned employee, job, due date range or overdue state.
- Update Contact
Updates an existing customer contact or site contact in Fergus.
- Update Customer
Updates an existing customer's details.
- Update Quote
Updates a draft quote on a Quote or Estimate job in Fergus: title, description and its sections with line items.
- Update Site
Updates an existing site's details.
- Update Task
Updates a task's description, due date, or assigned employees in Fergus. The job a task is linked to cannot be changed.
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 Groove
Groove to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Groove to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Groove to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Groove to MailchimpMailchimp marketing automation and email platform.
Groove to StripeStripe is a payment processing platform for online businesses.
Groove to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into Fergus
Outlook to FergusOutlook is Microsoft's email and calendaring platform integrating contacts and scheduling, enabling users to...
Google Sheets to FergusGoogle Sheets
Gmail to FergusGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Groove and Fergus, answered
What can start an automation from Groove?
Any of Groove's 9 triggers in the catalog, including Customer Added, Note Added, Agent Replied and Customer Replied. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Fergus when something happens in Groove?
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 Groove?
Fergus has no triggers in the catalog today, so automations start in Groove. 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 Groove 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 Groove 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.