--- title: "Connect Reply and Sorry - APIANT.ai" description: "When \"New Email Opened\" fires in Reply, your agent runs \"Update status page\" in Sorry, or \"New notice\" in Sorry to \"Add contact list\" in Reply." canonical: "https://apiant.ai/connect/reply-to-sorry" --- # Connect Reply and Sorry When **New Email Opened** fires in [Reply](https://apiant.ai/connections/reply), your agent runs **Update status page** in [Sorry](https://apiant.ai/connections/sorry), or **New notice** in Sorry to **Add contact list** in Reply. Describe the whole flow and it is built, tested on every scenario and kept running. Reply **7** triggers Reply **16** actions Sorry **1** trigger Sorry **16** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Reply and Sorry to do together? Give your AI client this address. `https://mcp.apiant.ai` One 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.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) Example flows ## What Reply and Sorry can do together ### From Reply to Sorry - When **New Email Opened** in Reply then **Update status page** in Sorry - When **New Emails Sent** in Reply then **Add component** in Sorry ### From Sorry to Reply - When **New notice** in Sorry then **Add contact list** in Reply - When **New notice** in Sorry then **Add note to contact** in Reply 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 Reply and Sorry ## Triggers and actions 8 triggers · 32 actions - Trigger **Inbox Category Set for Reply** Triggers when an email reply in Reply is given an inbox category, automatically or by a user. - Trigger **New Email Opened** Triggers when a contact opens a tracked email sent from Reply. - Trigger **New Emails Sent** Triggers when Reply sends an email from a sequence step. - Trigger **New Link Clicked** Triggers when a recipient clicks a tracked link in an email sent from Reply. - Trigger **New Person Bounce** Triggers when an email sent from Reply bounces or is rejected by the recipient's mail server. - Trigger **New Person Opt Out** Triggers when a contact opts out of outreach in Reply (unsubscribe link, manual opt-out, or marked Do Not Contact). - Trigger **Prospect Finished** Triggers when a contact's participation in a Reply sequence ends — completed, replied, bounced, opted out, or finished manually. - Action **Add contact list** Creates a new contact list in Reply, optionally shared with your team. - Action **Add note to contact** Adds a note to a contact's timeline in Reply. - Action **Add sequence** Creates a new sequence in Reply with its steps, schedule, sending accounts and settings. - Action **Create\Update Person** Creates a Reply contact, or updates the existing contact with the same email address. - Action **Delete contact** Deletes a contact from your Reply account. - Action **Find contacts by criteria** Returns the contacts that match a search term and/or field rules, optionally scoped to a contact list, sequence or sequence step. - Action **Get contact** Returns one Reply contact by its id, including profile details, owner, opt-out, call and meeting status, stage and custom fields. - Action **Get sequence** Returns one sequence in full: name, status, owner, schedule, settings, connected email and LinkedIn accounts, and its steps. - Action **List contact lists** Returns the contact lists you own plus those shared with your team, optionally filtered by name. - Action **List contacts** Returns your Reply contacts, optionally narrowed to one email address or LinkedIn profile URL. - Action **List inbox categories** Returns the inbox categories you can file conversations under. - Action **List Sequence Contacts** Returns the contacts enrolled in a sequence, with each contact's status, current step, added date, opt-out and call status. - Action **List sequences** Returns the sequences in your Reply account, optionally filtered by status, owner, folder, archive state or name. - Action **Mark as Finished** Marks one or more contacts as finished in every sequence they are in, so they receive no further sequence steps. - Action **Remove Person From Campaign** Removes a contact from a sequence so they stop progressing through it. The contact and their history stay in your Reply account. - Action **Send Test Webhook Event** Sends a test event from an existing Reply webhook subscription to its configured URL. - Trigger **New notice** Triggers when a new notice (incident, maintenance or general announcement) is created on the selected Sorry status page. - Action **Add component** Creates a new component on a Sorry status page, optionally nested under a parent component. - Action **Add notice** Creates a new incident, maintenance or general notice on a Sorry status page, optionally linking affected components and publishing it to subscribers. - Action **Add notice update** Posts a new update on an existing notice on a Sorry status page, optionally publishing it to your configured integrations. - Action **Add subscriber** Adds an email or SMS subscriber to a status page, optionally limited to specific components, so they receive status notices. - Action **Delete notice** Deletes a notice (incident, maintenance or general) from a Sorry status page. - Action **Delete subscriber** Permanently removes a subscriber from a status page. - Action **Get notice** Returns a single notice from a status page, including its type, state, subject, synopsis and link. - Action **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. - Action **List components** Returns all components (the services or infrastructure elements) shown on a Sorry status page, with their current state. - Action **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. - Action **List notice updates** Returns all updates posted on a notice on one of your Sorry status pages, optionally filtered by creation date or content. - Action **List status pages** Returns all status pages in your Sorry account, optionally filtered by name or creation date. - Action **List subscribers** Returns the subscribers on a status page, optionally only those who receive notices for a specific component. - Action **Update component** Updates a component on a Sorry status page, such as its name, description, position or parent component. - Action **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. - Action **Update status page** Updates a status page's settings, such as its name, timezone, support contact details, search visibility and language. ## Each app on its own - [ **Reply** Reply is a sales automation platform that puts outreach on autopilot, while still making each communication...](https://apiant.ai/connections/reply) - [ **Sorry** Status page and incident communication platform for notifying customers about downtime.](https://apiant.ai/connections/sorry) Reviews ## What our customers say ## More from Reply - [ **Reply to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/reply-to-salesforce) - [ **Reply to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/reply-to-slack) - [ **Reply to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/reply-to-stripe) - [ **Reply to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/reply-to-shopify) - [ **Reply to Trello** Trello is a visual collaboration tool that organizes projects into boards, lists, and cards.](https://apiant.ai/connect/reply-to-trello) - [ **Reply to Zoom** Zoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...](https://apiant.ai/connect/reply-to-zoom) ## More into Sorry - [ **HubSpot to Sorry** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-sorry) - [ **Salesforce to Sorry** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-sorry) - [ **Slack to Sorry** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-sorry) - [ **Google Sheets to Sorry** Google Sheets](https://apiant.ai/connect/google-sheets-to-sorry) - [ **Gmail to Sorry** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-sorry) - [ **Google Calendar to Sorry** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-sorry) Questions ## Reply and Sorry, answered ### ### What can start an automation from Reply? Any of Reply's 7 triggers in the catalog, including New Email Opened, New Emails Sent, New Link Clicked and New Person Bounce. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Sorry when something happens in Reply? 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 Reply? Yes. When something happens in Sorry, your agent can act in Reply too. This page covers both directions: Sorry's triggers and Reply's actions are listed here as well. ### ### Do I have to build a connector for Reply 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 Reply 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.