Integration
Connect Dux-Soup to Instatus
When New Dux-Soup Action Event fires in Dux-Soup, your agent runs Add component in Instatus. 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 Dux-Soup and Instatus 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 Dux-Soup can start in Instatus
When New Dux-Soup Action Event in Dux-Soup
then Add component in Instatus
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 Dux-Soup and Instatus
Triggers and actions 2 triggers · 27 actions
- New Dux-Soup Action Event
Triggers when Dux-Soup executes a queued LinkedIn action, such as a visit, connection request or message.
- New Profile Visit Event
Triggers when Dux-Soup visits and records a LinkedIn profile, with the person's name, title, company and tags.
- Find Contacts
Lists or searches the LinkedIn contacts Dux-Soup has recorded in a campaign, with name, title, company and tags.
- Get Campaign
Returns one Dux-Soup campaign with its action sequence, target and on/off status.
- Get Campaign Schema
Returns the action types, targets and text limits that are valid when building a Dux-Soup campaign.
- Get Campaign Stats
Returns the profiles active in a Dux-Soup campaign over a date range, with the funnel tags that show how far each has progressed.
- Get Conversation
Returns every message and LinkedIn event Dux-Soup has recorded for a prospect, in raw event form including the thread URL.
- Get Prospect Tags
Returns the tags on a prospect, including Dux-Soup's campaign funnel tags.
- Get Queue Size
Returns how many LinkedIn activities are waiting in the Dux-Soup queue, optionally for one campaign, profile or activity type.
- Get Recent Messages
Returns recent messages exchanged with a prospect, each with its time, direction and text.
- Get User Profile
Returns the connected Dux-Soup user's name, email address and account creation date.
- Get User Settings
Returns every Dux-Soup configuration setting for the connected user, such as daily limits, automation and exclusion rules.
- List Campaigns
Returns all of the user's Dux-Soup campaigns with their action sequences and on/off status.
- List Queued Items
Returns up to 100 LinkedIn activities waiting in the Dux-Soup queue, with the profile, campaign and scheduled time of each.
- List Recent Actions
Returns the LinkedIn actions Dux-Soup recently executed, with the profile, campaign, time and whether each succeeded.
- Add component
Creates a new component on an Instatus status page and returns the created component.
- Add incident update
Posts a new update to an existing incident on an Instatus status page, optionally changing the incident status and affected component statuses.
- Add maintenance
Schedules a new maintenance on an Instatus status page, with its affected components, timing and subscriber notification options.
- Add subscriber
Adds a subscriber (by email or phone) to a status page, subscribed to all components or to specific ones.
- Create Incident
Creates a new incident on an Instatus status page, optionally marking affected components and notifying subscribers.
- Delete incident
Deletes an incident from an Instatus status page.
- Get component
Returns one component on an Instatus status page, including its name, current status, description and group.
- Get incident
Returns a single incident on a status page, including its updates, affected components and the teammate who created it.
- Get maintenance
Returns one scheduled maintenance on a status page, including its updates and affected components.
- List components
Returns the components on an Instatus status page, with each component's name, status and group.
- List maintenances
Returns the scheduled, in-progress and completed maintenances on an Instatus status page.
- List status pages
Returns the status pages in your Instatus account, including each page's id, name, subdomain and current status.
- List subscribers
Returns the subscribers of an Instatus status page, optionally filtered by email/phone search or subscription status.
- Update component
Updates a component on an Instatus status page, such as its name, description, status, order or group.
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 Dux-Soup
Dux-Soup to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Dux-Soup to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Dux-Soup to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Dux-Soup to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Dux-Soup to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Dux-Soup to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Instatus
Questions
Dux-Soup and Instatus, answered
What can start an automation from Dux-Soup?
Any of Dux-Soup's 2 triggers in the catalog, including New Dux-Soup Action Event and New Profile Visit Event. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Instatus when something happens in Dux-Soup?
Any of Instatus's 14 actions, including Create Incident, Update component, Add component and Add incident update. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Instatus to Dux-Soup?
Instatus has no triggers in the catalog today, so automations start in Dux-Soup. If you need the other direction, ask: your agent reads Instatus's API documentation and adds it.
Do I have to build a connector for Dux-Soup or Instatus?
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 Dux-Soup and Instatus 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.