Integration
Connect CONSENSUS and Sorry
When New Lead fires in CONSENSUS, your agent runs Update status page in Sorry, or New notice in Sorry to Create Lead in CONSENSUS. 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 CONSENSUS and Sorry 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 CONSENSUS and Sorry can do together
From CONSENSUS to Sorry
When New Lead in CONSENSUS
then Update status page in Sorry
From Sorry to CONSENSUS
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 CONSENSUS and Sorry
Triggers and actions 3 triggers · 31 actions
- Demo Watched
Triggers when a demo you sent from Sales Accelerator is watched again (its view count goes up).
- New Lead
Triggers when a new lead is captured in Consensus, such as a viewer filling out a demo's lead form.
- Create Demo Link
Creates a marketing share link for a demo.
- Create Lead
Creates a lead in Consensus from a contact's name, email and company.
- Create Mail Merge Link
Creates a mail merge link for a demo using your email platform's merge tags.
- Delete Recipient
Deletes a demo recipient and their data by email address.
- Find Leads
Returns leads captured by your demos, optionally filtered by email address or date range.
- Find Recipient
Finds a demo recipient by email address.
- Find Sent Demos
Returns the demos your team has sent to prospects, with their view counts and recipients.
- Get Current User
Returns the Consensus user this connection acts as and their organization.
- Get Demo by Link Hash
Returns the demo that a Consensus share link points to.
- Get Mail Merge Link
Returns one mail merge link.
- List Mail Merge Links
Returns your mail merge links.
- List Mail Merge Platforms
Returns the email platforms you can build mail merge links for.
- Search Demos
Returns the demos whose title matches your search text, with their preview links and owners.
- Send Demo
Sends a demo to a prospect contact and returns the personal share link.
- Update Sent Demo
Updates the company or opportunity on a demo you sent.
- New notice
Triggers when a new notice (incident, maintenance or general announcement) is created on the selected Sorry status page.
- Add component
Creates a new component on a Sorry status page, optionally nested under a parent component.
- Add notice
Creates a new incident, maintenance or general notice on a Sorry status page, optionally linking affected components and publishing it to subscribers.
- Add notice update
Posts a new update on an existing notice on a Sorry status page, optionally publishing it to your configured integrations.
- Add subscriber
Adds an email or SMS subscriber to a status page, optionally limited to specific components, so they receive status notices.
- Delete notice
Deletes a notice (incident, maintenance or general) from a Sorry status page.
- Delete subscriber
Permanently removes a subscriber from a status page.
- Get notice
Returns a single notice from a status page, including its type, state, subject, synopsis and link.
- Get status page
Returns a single Sorry status page with its name, state, timezone, support details and notification settings, optionally including related brand, components, notices and more.
- List components
Returns all components (the services or infrastructure elements) shown on a Sorry status page, with their current state.
- List notices
Returns the notices (incidents, maintenance and general notices) posted on a Sorry status page, optionally filtered by type, state, subject or creation date.
- List notice updates
Returns all updates posted on a notice on one of your Sorry status pages, optionally filtered by creation date or content.
- List status pages
Returns all status pages in your Sorry account, optionally filtered by name or creation date.
- List subscribers
Returns the subscribers on a status page, optionally only those who receive notices for a specific component.
- Update component
Updates a component on a Sorry status page, such as its name, description, position or parent component.
- Update notice
Updates an existing notice on a Sorry status page — change its subject or state, add a comment, set affected components or reschedule planned maintenance.
- Update status page
Updates a status page's settings, such as its name, timezone, support contact details, search visibility and language.
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 CONSENSUS
CONSENSUS to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
CONSENSUS to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
CONSENSUS to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
CONSENSUS to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
CONSENSUS to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
CONSENSUS to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Sorry
Questions
CONSENSUS and Sorry, answered
What can start an automation from CONSENSUS?
Any of CONSENSUS's 2 triggers in the catalog, including New Lead and Demo Watched. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Sorry when something happens in CONSENSUS?
Any of Sorry's 16 actions, including Update component, Update notice, Update status page and Add component. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Sorry to CONSENSUS?
Yes. When something happens in Sorry, your agent can act in CONSENSUS too. This page covers both directions: Sorry's triggers and CONSENSUS's actions are listed here as well.
Do I have to build a connector for CONSENSUS or Sorry?
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 CONSENSUS and Sorry 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.