Integration
Connect Whippy to Clicksign
When Channels fires in Whippy, your agent runs Notifications Email in Clicksign. 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 Whippy and Clicksign 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 Whippy can start in Clicksign
When Channels in Whippy
then Notifications Email in Clicksign
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 Whippy and Clicksign
Triggers and actions 4 triggers · 31 actions
- Channels
Triggers when a new channel is added to your Whippy organization.
- List Agents
Triggers when a new AI agent is added to your Whippy organization.
- List Calls
Triggers when a new call is logged in Whippy.
- List Users
Triggers when a new user is added to your Whippy organization.
- Add Contacts to a Sequence
Adds contacts to a Whippy sequence, creating any contact that does not exist yet.
- Create a Contact
Creates a new contact in Whippy from a phone number, with optional name, email and opt-in preferences.
- Delete a Contact
Deletes a contact from Whippy by its ID.
- Get Agent by ID
Returns one Whippy AI agent by its ID, including its current version and settings.
- Get All Campaigns
Returns the campaigns in your Whippy organization, optionally filtered by title.
- Get All Channels
Returns the channels (phone numbers, email addresses and other locations) in your Whippy organization.
- Get All Contacts
Returns the contacts in your Whippy organization, optionally filtered by name, email or phone.
- Get All Sequences
Returns the sequences in your Whippy organization, optionally filtered by title.
- Get All Sequence Steps
Returns all the steps of a Whippy sequence, including each step's message and delivery stats.
- Get Call by ID
Returns one Whippy call by its ID, including its recording and transcript links.
- Get Campaign by ID
Returns one Whippy campaign by its ID.
- Get Campaign Contacts
Returns the contacts a Whippy campaign was sent to, with optional filters for delivery, responses, unsubscribes and link clicks.
- Get Contact by ID
Returns one Whippy contact by its ID.
- Get Contacts in a Sequence
Returns the contacts enrolled in a Whippy sequence, with optional filters for status, step, responses, unsubscribes and link clicks.
- Get Sequence by ID
Returns one Whippy sequence by its ID.
- List Agents
Returns the AI agents in your Whippy organization, optionally filtered by name.
- List Calls
Returns calls in your Whippy organization, optionally limited to a date range.
- List Users
Returns the users in your Whippy organization, optionally filtered by name, email, phone, role or state.
- Send an SMS
Sends an SMS text message from one of your Whippy channels to a phone number.
- Update a Contact
Updates an existing Whippy contact's details such as name, email, phone or opt-in preferences.
- Create Signer
Creates a signer on a Clicksign envelope and returns the new signer record, ready to be linked to the envelope's documents.
- Delete Document
Deletes a draft document from a Clicksign envelope.
- Delete Signer
Deletes a signer from an envelope, as long as the signer has not started signing.
- List Documents
Returns the documents in a Clicksign envelope, with each document's status, file name and download link.
- List Templates
Returns the document templates (modelos) in your Clicksign account.
- Notifications Email
Sends a signer a notification asking them to sign an envelope, with an optional custom message and email wording. Returns the notification and whether the signer was notified.
- Notifications SMS
Re-sends the signing notification to a signer of an envelope, delivered over the channel the signer is set up for (SMS for SMS signers), with an optional custom message.
- Notifications WhatsApp
Sends a reminder to a signer on an envelope through the WhatsApp channel configured for that signer, and returns whether the signer was notified.
- Remove Signer From Document
Removes a signer who has not yet started signing from a Clicksign envelope.
- View Document
Returns the current details and status of a document inside a Clicksign envelope.
- View Signer
Returns the current details of a signer on a Clicksign envelope, including name, email, phone number and notification preferences.
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 Whippy
Whippy to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Whippy to WixThe Wix website builder gives businesses of any size the tools to create, manage and grow a fully integrated...
Whippy to LinkedInLinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...
Whippy to FacebookFacebook is a social media and advertising platform used by individuals and businesses to connect, share...
Whippy to AnthropicAnthropic builds Claude, a family of large language models.
Whippy to SupabaseSupabase is an open-source backend-as-a-service providing a Postgres database, authentication, storage, and...
More into Clicksign
HubSpot to ClicksignHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to ClicksignSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to ClicksignSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to ClicksignGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to ClicksignGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ClicksignGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Whippy and Clicksign, answered
What can start an automation from Whippy?
Any of Whippy's 4 triggers in the catalog, including Channels, List Agents, List Calls and List Users. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Clicksign when something happens in Whippy?
Any of Clicksign's 11 actions, including Create Signer, List Documents, List Templates and Notifications Email. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Clicksign to Whippy?
Clicksign has no triggers in the catalog today, so automations start in Whippy. If you need the other direction, ask: your agent reads Clicksign's API documentation and adds it.
Do I have to build a connector for Whippy or Clicksign?
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 Whippy and Clicksign 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.