Integration
Connect Crove to Mailshake
When Document Completed fires in Crove, your agent runs Add Recipient by Email Address in Mailshake. 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 Crove and Mailshake 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 Crove can start in Mailshake
When Document Completed in Crove
then Add Recipient by Email Address in Mailshake
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 Crove and Mailshake
Triggers and actions 2 triggers · 19 actions
- Document Completed
Triggers when a Crove document is completed.
- Document Created
Triggers when a new document is created in Crove.
- Create Document
Creates a new document from a Crove template, optionally pre-filling field values.
- Generate PDF From Document
Starts a PDF, DOCX or audit-trail export of a Crove document and returns the export job.
- Get Document Details
Returns one Crove document with its status and field values.
- Get Export
Returns the status of a Crove export job and its signed download URL when ready.
- Get Template
Returns one Crove template with its fields and signer roles.
- List Documents
Returns Crove documents, optionally filtered by template, name, sent or completed status.
- List Templates
Returns the templates in your Crove workspace, with their fields and signer roles.
- Send Document
Sends a Crove document to a recipient for signing or filling and emails them a secure link.
- Submit Document
Submits a Crove document on behalf of the workspace, marking it completed.
- Update Document
Updates field values on an existing Crove document.
- Add Recipient by Email Address
Adds one recipient to a Mailshake campaign. This can cause emails to be sent immediately.
- Add Recipients by Email Addresses
Adds several recipients to a Mailshake campaign from a list of email addresses. This can cause emails to be sent immediately.
- Add Recipients From CSV
Adds recipients to a Mailshake campaign from CSV text; each column can be used as a text replacement. This can cause emails to be sent immediately.
- Create Campaign
Creates a new Mailshake campaign. It cannot send until finished in Mailshake, but recipients can be added.
- Get Campaign
Returns one Mailshake campaign and its message sequence.
- Get Lead
Returns one Mailshake lead with its recipient, campaign and status.
- Get Recipient
Returns one recipient of a Mailshake campaign, looked up by email address.
- List Campaigns
Returns your team's Mailshake campaigns, optionally filtered by a search term.
- Unsubscribe Recipients
Unsubscribes one or more email addresses from all current and future Mailshake campaigns for your team.
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 Crove
Crove to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Crove to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Crove to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Crove to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Crove to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Crove to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Mailshake
Questions
Crove and Mailshake, answered
What can start an automation from Crove?
Any of Crove's 2 triggers in the catalog, including Document Completed and Document Created. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Mailshake when something happens in Crove?
Any of Mailshake's 9 actions, including Create Campaign, Add Recipient by Email Address, Add Recipients by Email Addresses and Add Recipients From CSV. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Mailshake to Crove?
Mailshake has no triggers in the catalog today, so automations start in Crove. If you need the other direction, ask: your agent reads Mailshake's API documentation and adds it.
Do I have to build a connector for Crove or Mailshake?
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 Crove and Mailshake 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.