Integration
Connect Pyrus and Skyvern
When New Form Task fires in Pyrus, your agent runs Get a Task in Skyvern, or New or Updated Skyvern Workflow in Skyvern to Add Task Comment in Pyrus. 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 Pyrus and Skyvern 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 Pyrus and Skyvern can do together
From Pyrus to Skyvern
When New Form Task in Pyrus
then Get a Task in Skyvern
When New Form Task in Pyrus
then Create and Run a Task in Skyvern
From Skyvern to Pyrus
When New or Updated Skyvern Workflow in Skyvern
then Add Task Comment in Pyrus
When New or Updated Skyvern Workflow in Skyvern
then Find Form Tasks in Pyrus
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 Pyrus and Skyvern
Triggers and actions 2 triggers · 26 actions
Trigger
New Form TaskTriggers when a new task is created from a Pyrus form.
Action
Add MemberAdds a user to the Pyrus organization.
Action
Add Task CommentAdds a comment to a Pyrus task, and can also close or reopen it, approve or reject it, or reassign it.
Action
Delete TaskDeletes a Pyrus task.
Action
Find Catalog ItemsReturns a Pyrus catalog's items, optionally only those whose column matches a value.
Action
Find Form TasksSearches the tasks created from a Pyrus form, by text, step, or creation and modification dates.
Action
Get FormReturns a Pyrus form template with its fields.
Action
Get MemberReturns a Pyrus organization member's profile by ID.
Action
Get TaskReturns a Pyrus task with its fields, participants and comments.
Action
List CatalogsReturns all Pyrus catalogs, without their items.
Action
List FormsReturns all Pyrus form templates the user manages or belongs to.
Action
List MembersReturns all members of the Pyrus organization.
Trigger
New or Updated Skyvern WorkflowTriggers when a Skyvern workflow (agent) is created or a new version of it is saved.
Action
Add browser sessionCreates a Skyvern browser session that persists across multiple task and workflow runs, and returns its session id and live-view link.
Action
Add credentialCreates a new stored credential (login, credit card or secret) in your Skyvern organization for use by tasks and agents.
Action
Add workflowCreates a new Skyvern workflow (agent) from a JSON or YAML definition and returns the saved workflow.
Action
Cancel runCancels a running Skyvern task run or workflow run by its id.
Action
Create and Run a TaskStarts a Skyvern browser-automation task from a plain-language prompt and returns the new run, including its id, status and link in the Skyvern app.
Action
Create and Run Task V2Starts a Skyvern 2.0 browser task from a natural-language prompt and returns the new run's id and status.
Action
Delete workflowDeletes a Skyvern workflow (agent) by its ID.
Action
Get a Browser SessionReturns the details of a Skyvern browser session, including its status, browser address for connecting, downloaded files and recordings.
Action
Get a TaskReturns a Skyvern task run by its id, including its status, extracted output, downloaded files, recording and screenshots.
Action
Get a Task V2Returns the status, output, recording and screenshots of a Skyvern task run.
Action
Get a WorkflowReturns a Skyvern workflow (agent) by its permanent id, including its blocks, parameters and settings.
Action
List credentialsReturns the credentials stored in your Skyvern organization, optionally filtered by vault, type or search text. Secrets are never included.
Action
List runsReturns your organization's task and agent runs, newest first, optionally filtered by status, run type, agent, tags, failure category or a search term.
Action
List workflowsReturns the workflows (agents) in your Skyvern organization, optionally filtered by search text, folder, status or tags. Returns up to 100 workflows.
Action
Run a WorkflowStarts a run of one of your Skyvern workflows (agents) with the parameters you supply, and returns the new run's id, status and link.
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 Pyrus
Pyrus to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Pyrus to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Pyrus to StripeStripe is a payment processing platform for online businesses.
Pyrus to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Pyrus to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Pyrus to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
More into Skyvern
HubSpot to SkyvernHubSpot is your all-in-one stop for all of your marketing software needs.
CentralStationCRM to SkyvernCentralStationCRM is an easy CRM software. We focus on ease of use, collaboration and work best when you...
Cliniko to SkyvernCliniko is a practice management platform — manage patients, appointments, invoices, contacts, and...
Salesforce to SkyvernSalesforce is a leading enterprise customer relationship management (CRM) platform.
Google Sheets to SkyvernGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to SkyvernGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Pyrus and Skyvern, answered
What can start an automation from Pyrus?
Any of Pyrus's 1 trigger in the catalog, including New Form Task. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Skyvern when something happens in Pyrus?
Any of Skyvern's 15 actions, including Create and Run a Task, Create and Run Task V2, Add browser session and Add credential. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Skyvern to Pyrus?
Yes. When something happens in Skyvern, your agent can act in Pyrus too. This page covers both directions: Skyvern's triggers and Pyrus's actions are listed here as well.
Do I have to build a connector for Pyrus or Skyvern?
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 Pyrus and Skyvern 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.