Integration
Connect Pipefile and Channels
When something happens in Pipefile or Channels, your agent does the next thing in the other. Describe it 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 Channels to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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)Pipefile handles the back and forth of collecting sensitive documents, while Channels handles the calls about them. Joining the two means a file request in Pipefile can create or update the matching contact in Channels, and a finished call or voicemail in Channels can start a request or add the caller to Pipefile.
Example flows
What Pipefile and Channels can do together
From Pipefile to Channels
When File Request Created in Pipefile
then Delete number from do-not-call list in Channels
When File Request Created in Pipefile
then Update contact in Channels
From Channels to Pipefile
When New Voicemail Left in Channels
then Create Contact in Pipefile
When New Call Finished in Channels
then Get File Request 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 Channels
Triggers and actions 3 triggers · 19 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 Call FinishedTriggers when a call is finished.
Trigger
New Voicemail LeftAction
Add note to contactAdd a note to a contact's history.
Action
Add number to do-not-call listBlock a phone number by adding it to the Do Not Call list.
Action
Create New ContactCreates a new Contact in your Channels account.
Action
Delete contactDelete a contact by id.
Action
Delete number from do-not-call listUnblock a phone number by removing it from the Do Not Call list.
Action
Get account balanceRetrieve the account's current finance balance.
Action
Get contactRetrieve a single contact by id.
Action
List contactsList all contacts on the account.
Action
Update contactUpdate an existing contact's fields.
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 Google AnalyticsGoogle Analytics tracks and reports website traffic, user behavior, and conversion data, enabling marketers...
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...
Pipefile to StripeStripe is a payment processing platform for online businesses.
Pipefile to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Pipefile to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Channels
ActiveCampaign to ChannelsActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to ChannelsOrganize anything with Airtable, a modern database created for everyone.
Asana to ChannelsAsana is a collaborative information manager for workspace.
Brevo to ChannelsBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
Calendly to ChannelsCalendly is a scheduling automation platform for eliminating the back-and-forth emails to find the perfect...
YouTube to ChannelsYouTube is a video-sharing platform with user-generated content, live streaming, and monetization...
Questions
Pipefile and Channels, answered
Can a call in Channels start a document request in Pipefile?
Yes. A finished call in Channels can create a file request from one of your Pipefile templates for the person you spoke with, and a voicemail can add the caller to your Pipefile contacts. The agent tests every scenario before it goes live.
What happens if the caller is not already a contact in Channels?
The agent can list contacts in Channels to check, then create the contact when no match comes back and add a note to their history. If the contact already exists, it updates the existing record instead of making a duplicate.
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 Channels when something happens in Pipefile?
Any of Channels's 9 actions, including Delete number from do-not-call list, Update contact, Create New Contact and Add note to contact. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Channels to Pipefile?
Yes. When something happens in Channels, your agent can act in Pipefile too. This page covers both directions: Channels's triggers and Pipefile's actions are listed here as well.
Do I have to build a connector for Pipefile or Channels?
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.
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.