Integration
Connect Cisco Spark and Sorry
When New membership fires in Cisco Spark, your agent runs Update status page in Sorry, or New notice in Sorry to Add message in Cisco Spark. 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 Cisco Spark 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 Cisco Spark and Sorry can do together
From Cisco Spark to Sorry
When New membership in Cisco Spark
then Update status page in Sorry
From Sorry to Cisco Spark
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 Cisco Spark and Sorry
Triggers and actions 4 triggers · 32 actions
- New membership
Triggers when someone joins a Webex space you are in, or you are added to a space.
- New message
Triggers when a new message is posted in a Webex space the connected account can see.
- New space
Triggers when a new Webex space is created.
- Add membership
Adds a person to a Webex space, by person ID or email, optionally as a moderator.
- Add message
Posts a message to a Webex space, or as a direct message to a person, with optional text, markdown, file and card attachments.
- Add space
Creates a new Webex space, optionally inside a team.
- Add team
Creates a new team in Webex.
- Delete membership
Removes a person from a Webex space by deleting their membership.
- Delete message
Deletes a message from a Webex space.
- Delete space
Deletes a Webex space (room) by its ID.
- Find people by email or name
Finds Webex people by email address or display name and returns the matching people.
- Get message
Returns the details of a single Webex message, including its text, sender, space and attachments.
- Get person
Returns the details of a Webex person, such as their name, emails and status, by their person ID.
- Get space
Returns the details of a Webex space, such as its title, type and when it was created.
- List memberships
Returns the memberships of a Webex space, or your own memberships, optionally filtered by person.
- List messages
Returns the messages posted in a Webex space, optionally filtered to a thread, mentions, or a point in time.
- List spaces
Returns the Webex spaces you belong to, optionally filtered by team or space type.
- List teams
Returns the Webex teams you belong to.
- Update space
Updates a Webex space's title, description, moderation, visibility and other settings.
- 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 Cisco Spark
Cisco Spark to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Cisco Spark to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Cisco Spark to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Cisco Spark to Google SheetsGoogle Sheets
Cisco Spark to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Cisco Spark to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Sorry
Questions
Cisco Spark and Sorry, answered
What can start an automation from Cisco Spark?
Any of Cisco Spark's 3 triggers in the catalog, including New membership, New message and New space. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Sorry when something happens in Cisco Spark?
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 Cisco Spark?
Yes. When something happens in Sorry, your agent can act in Cisco Spark too. This page covers both directions: Sorry's triggers and Cisco Spark's actions are listed here as well.
Do I have to build a connector for Cisco Spark 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 Cisco Spark 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.