Integration
Connect Groove to Attentive
When Customer Added fires in Groove, your agent runs Custom Events in Attentive. 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 Attentive 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 Attentive
When Customer Added in Groove
then Custom Events in Attentive
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 Attentive
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.
- Add to Cart
Records that a shopper added a product to their cart in Attentive, so cart-abandonment journeys can fire.
- Custom Attributes
Sets custom attributes (such as age, birthday or favorite team) on an Attentive user identified by phone, email, or external identifier.
- Custom Events
Sends a custom event (such as "Order Shipped") for a user to Attentive, which can trigger Journeys.
- Delete Request
Creates a privacy (CCPA) deletion request that deletes a subscriber within thirty days, identified by email, phone or client user id.
- Get Custom Attributes for a User
Returns all custom attributes (name and value) stored on an Attentive user, looked up by phone number or email.
- Get Subscription Eligibility for a User
Returns the subscription types and channels (SMS or email) a subscriber is eligible to receive messages on, looked up by phone number or email.
- Identity
Associates a client user identifier or custom identifiers with an Attentive subscriber identified by phone, email, Shopify ID or Klaviyo ID.
- Lookup Product Catalog Ingestion
Returns the status, validation errors and product counts of a product catalog upload.
- Product View
Records that a shopper viewed one or more products in Attentive, so product-view journeys can fire.
- Purchase
Records a purchase (order) event for a shopper in Attentive so it can trigger purchase-based journeys.
- Subscribe User
Opts a person in to Attentive text or email subscriptions by phone or email, using a sign-up unit or a locale and subscription type.
- Unsubscribe Subscriptions for a User
Unsubscribes a user (by phone or email) from specific Attentive subscription types and channels, or from all subscriptions when none are given.
- View Recent Catalog Uploads
Returns your recent product catalog uploads with their ingestion status, product counts and validation errors, newest first.
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 Attentive
Google Sheets to AttentiveGoogle Sheets
Gmail to AttentiveGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to AttentiveGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Groove and Attentive, 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 Attentive when something happens in Groove?
Any of Attentive's 13 actions, including Add to Cart, Custom Attributes, Custom Events and Get Custom Attributes for a User. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Attentive to Groove?
Attentive has no triggers in the catalog today, so automations start in Groove. If you need the other direction, ask: your agent reads Attentive's API documentation and adds it.
Do I have to build a connector for Groove or Attentive?
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 Attentive 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.