Integration
Connect Pipefile and Skyvern
When File Request Created fires in Pipefile, your agent runs Create and Run a Task in Skyvern, or New or Updated Skyvern Workflow in Skyvern to Create Contact in Pipefile. 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 Pipefile 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)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 Pipefile and Skyvern can do together
From Pipefile to Skyvern
When File Request Created in Pipefile
then Create and Run a Task in Skyvern
When File Request Created in Pipefile
then Create and Run Task V2 in Skyvern
From Skyvern to Pipefile
When New or Updated Skyvern Workflow in Skyvern
then Create Contact in Pipefile
When New or Updated Skyvern Workflow in Skyvern
then Update Contact in Pipefile
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 Pipefile and Skyvern
Triggers and actions 2 triggers · 25 actions
Trigger
File Request CreatedTriggers when a file request is created.
Action
Add File Request From TemplateCreate a new file request from an existing template for one recipient (name/email/phone), optionally on behalf of a team member via X-Pipefile-On-Behalf-Of.
Action
Create ContactAdd to contacts
Action
Delete ContactDelete a contact by id. Returns 204 No Content on success.
Action
Get ContactRetrieve one contact by id.
Action
Get File RequestRetrieve detailed information about one file request by id, including contents, items, files, and tracking events.
Action
List ContactsRetrieve a paginated list of contacts, filterable by name/email/phone partial match.
Action
List File Request TemplatesRetrieve the list of file request templates available for creating new file requests, with optional name search.
Action
Search File RequestsFinds all file requests matching this search query (contact name, email, tags, etc).
Action
Send RequestCreate and send a new request
Action
Update ContactUpdate name/email/phone of an existing contact by id.
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 Pipefile
Pipefile to ChannelsChannels is a data-driven phone system that lets you make and take calls directly in the browser.
Pipefile to CleanvoiceAPI that removes filler words, silences, background noise, and mouth sounds from audio and video recordings.
Pipefile to DeBounceDeBounce is an email verification service that allows you to validate your email addresses and remove...
Pipefile to DisifyDisify checks email addresses for disposable and temporary providers.
Pipefile to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Pipefile to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
More into Skyvern
HubSpot to SkyvernHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SkyvernSalesforce is a leading enterprise customer relationship management (CRM) platform.
Google Sheets to SkyvernGoogle Sheets
Gmail to SkyvernGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SkyvernGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to SkyvernGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Questions
Pipefile and Skyvern, answered
What can start an automation from Pipefile?
Any of Pipefile's 1 trigger in the catalog, including File Request Created. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Skyvern when something happens in Pipefile?
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 Pipefile?
Yes. When something happens in Skyvern, your agent can act in Pipefile too. This page covers both directions: Skyvern's triggers and Pipefile's actions are listed here as well.
Do I have to build a connector for Pipefile 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 Pipefile 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.