Integration
Connect Groove to Strava
When Customer Added fires in Groove, your agent runs Get activity in Strava. 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 Strava 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 Strava
When Customer Added in Groove
then Get activity in Strava
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 Strava
Triggers and actions 9 triggers · 28 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.
- Get activity
Returns the full details of one of the authenticated athlete's Strava activities, including distance, times, elevation, laps, splits and segment efforts.
- Get athlete
Returns the profile of the Strava athlete whose account is connected, including name, location, follower counts, clubs, bikes and shoes.
- Get athlete stats
Returns an athlete's activity totals — recent (last 4 weeks), year-to-date and all-time ride, run and swim stats, plus their longest ride and biggest climb. Only activities visible to Everyone are counted.
- Get club
Returns the full details of a Strava club, including its name, location, sport type, member count and your membership status.
- Get gear
Returns a piece of the athlete's equipment (a bike or pair of shoes) by its id, including brand, model, description and total distance.
- Get route
Returns a Strava route by its id, including its name, distance, elevation gain, map and segments. Private routes require read_all access.
- Get segment
Returns a Strava segment's details, including distance, grade, elevation, location, and the athlete's own stats on it.
- List activities
Returns the connected athlete's activities, newest first, optionally limited to a time window.
- List activity comments
Returns the comments posted on a Strava activity, including each comment's text, author and posting time.
- List activity kudoers
Returns the athletes who gave kudos to a Strava activity.
- List clubs
Returns the clubs the connected Strava athlete is a member of.
- List routes
Returns the routes created by the authenticated Strava athlete. Private routes are included only when the connection has read_all access.
- List starred segments
Returns the segments the connected Strava athlete has starred. Private segments are included only when the connection has the read_all scope.
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 Strava
Google Sheets to StravaGoogle Sheets
Gmail to StravaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to StravaGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Groove and Strava, 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 Strava when something happens in Groove?
Any of Strava's 13 actions, including Get activity, Get athlete, Get athlete stats and Get club. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Strava to Groove?
Strava has no triggers in the catalog today, so automations start in Groove. If you need the other direction, ask: your agent reads Strava's API documentation and adds it.
Do I have to build a connector for Groove or Strava?
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 Strava 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.