Integration
Connect Groove and Jenkins
When Customer Added fires in Groove, your agent runs Add job by copying in Jenkins, or New build in Jenkins to Add label to ticket in Groove. 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 Jenkins 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 and Jenkins can do together
From Groove to Jenkins
When Customer Added in Groove
then Add job by copying in Jenkins
When Note Added in Groove
then Build Job in Jenkins
From Jenkins to Groove
When New build in Jenkins
then Add label to ticket in Groove
When New Job in Jenkins
then Add message in Groove
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 Jenkins
Triggers and actions 12 triggers · 28 actions
Trigger
Agent RepliedTriggers when an agent replies to a ticket.
Trigger
Customer AddedTriggers when a customer is created.
Trigger
Customer RepliedTriggers when a customer replies to a ticket.
Trigger
Note AddedTriggers when a note is added to a ticket.
Trigger
Ticket AssignedTriggers when a ticket is assigned.
Trigger
Ticket ClosedTriggers when a ticket is closed.
Trigger
Ticket OpenedTriggers when a ticket is opened.
Trigger
Ticket StartedTriggers when a new ticket is created.
Trigger
Ticket TaggedTriggers when a ticket is tagged.
Action
Add label to ticketAdds one or more labels to a Groove ticket, keeping its existing labels, and returns the updated ticket.
Action
Add messageAdds a new message (reply or private note) to an existing Groove ticket.
Action
Add NoteAdds a private note to a Groove ticket, visible only to agents.
Action
Change Assigned AgentAssigns a Groove ticket to a different agent, identified by the agent's email address.
Action
Change Ticket MailboxMoves a ticket into a different mailbox.
Action
Change Ticket StateChanges the state of a Groove ticket (unread, opened, pending, closed or spam).
Action
Close TicketCloses a Groove ticket by setting its state to closed.
Action
Create New TicketCreates a new ticket in Groove from a customer or agent, with its first message.
Action
Get customerReturns one Groove customer, looked up by email address, including their contact details and custom attributes.
Action
Get ticketReturns a single Groove ticket by its ticket number.
Action
List agentsReturns the agents on your Groove account, optionally limited to one group.
Action
List mailboxesReturns all mailboxes in the Groove account, with each mailbox's name and email address.
Action
List messagesReturns the messages and notes on a Groove ticket.
Action
Reopen TicketReopens a Groove ticket by setting its state to opened.
Action
Update customerUpdates a customer's profile details, such as name, company, title and contact info, identified by their email address.
Trigger
New buildTriggers when a new build of the chosen Jenkins job starts.
Trigger
New JobTriggers when a new job is added to your Jenkins server.
Trigger
New Job Status NotificationTriggers when a job starts a new build.
Action
Add job by copyingCreates a new Jenkins job by copying the configuration of an existing job.
Action
Build JobStarts a new build of a job, optionally with build parameters. The build is queued and the queue item's location is returned.
Action
Delete JobPermanently deletes a job and its build history.
Action
Delete queue itemRemoves a waiting item from a pipeline's build queue so it never runs.
Action
Disable JobDisables a job so it no longer builds.
Action
Enable JobEnables a disabled job so it can be built again.
Action
Get JobReturns a job's details, including its builds, health and last build results.
Action
Get Last BuildReturns the most recent build of a job, with its number, result, duration and whether it is still running.
Action
List buildsReturns every build of a Jenkins job, newest first, with each build's number, result and timing.
Action
List JobsReturns the jobs on your Jenkins server with each job's name, URL and status color.
Action
List NodesReturns the build agents (nodes) on the Jenkins server with whether each is online and idle.
Action
List Queue ItemsReturns the builds waiting in the Jenkins build queue.
Action
Stop Last BuildAborts the most recent build of a job if it is still running.
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 AdyntelAd intelligence API that finds which LinkedIn, Google, and Meta ads a target company is running.
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.
More into Jenkins
HubSpot to JenkinsHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to JenkinsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to JenkinsGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to JenkinsGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to JenkinsGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to JenkinsActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
Groove and Jenkins, 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 Jenkins when something happens in Groove?
Any of Jenkins's 13 actions, including Add job by copying, Build Job, Disable Job and Enable Job. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Jenkins to Groove?
Yes. When something happens in Jenkins, your agent can act in Groove too. This page covers both directions: Jenkins's triggers and Groove's actions are listed here as well.
Do I have to build a connector for Groove or Jenkins?
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 Jenkins 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.