Integration
Connect Planports and Sorry
When New Contact fires in Planports, your agent runs Update status page in Sorry, or New notice in Sorry to Update contact in Planports. 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 Planports 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 Planports and Sorry can do together
From Planports to Sorry
When New Contact in Planports
then Update status page in Sorry
From Sorry to Planports
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 Planports and Sorry
Triggers and actions 2 triggers · 27 actions
- New Contact
Triggered when a new contact, either an individual or an organization, is added in Planports.
- Add meeting
Creates a meeting record in Planports, with its type, content, schedule, participants and links to a project or opportunity.
- Add proposal
Creates a sales proposal for a Planports contact, optionally with product lines.
- Find contact by phone number
Finds a Planports contact by phone number and returns the matching contact.
- List contacts
Returns all contacts in the Planports account, both individuals and organizations, optionally filtered by type, state, name or tag and sorted by name or date added.
- List meetings
Returns meetings in Planports, optionally filtered by owner, date, conclusion, subject or content.
- List products
Returns the products in the Planports account, optionally filtered by text, product code, product name or date added, and sorted as requested.
- List projects
Returns the projects in your Planports account, optionally filtered by project name.
- List proposals
Returns proposals from Planports, optionally filtered by customer name, proposal number, type, state, date range or the user who added them.
- List tasks
Returns the tasks in your Planports account, optionally filtered by project, stage or task detail.
- Update contact
Updates an existing contact (person or organization) in Planports.
- Update opportunity
Updates an existing opportunity in Planports. Only the fields you fill in are changed.
- 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 Planports
Planports to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Planports to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Planports to StripeStripe is a payment processing platform for online businesses.
Planports to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Planports to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Planports to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
More into Sorry
HubSpot to SorryHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to SorryGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to SorryGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SorryGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Planports and Sorry, answered
What can start an automation from Planports?
Any of Planports's 1 trigger in the catalog, including New Contact. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Sorry when something happens in Planports?
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 Planports?
Yes. When something happens in Sorry, your agent can act in Planports too. This page covers both directions: Sorry's triggers and Planports's actions are listed here as well.
Do I have to build a connector for Planports 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 Planports 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.