Integration
Connect Pipefile and SigParser
When File Request Created fires in Pipefile, your agent runs Upsert Contact in SigParser, or New Companies in SigParser 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 SigParser 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 Pipefile and SigParser can do together
From Pipefile to SigParser
When File Request Created in Pipefile
then Upsert Contact in SigParser
When File Request Created in Pipefile
then Find Contacts in SigParser
From SigParser to Pipefile
When New Companies in SigParser
then Create Contact in Pipefile
When New Contacts in SigParser
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 SigParser
Triggers and actions 5 triggers · 15 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 CompaniesTriggers when a SigParser company is created or meaningfully updated.
Trigger
New ContactsTriggers when a SigParser contact is created or meaningfully updated.
Trigger
New emailsTriggers when a new email is found across your team's SigParser mailboxes.
Trigger
New meetingsTriggers when a new meeting is found across your team's connected mailboxes.
Action
Find CompaniesReturns SigParser companies, optionally filtered by email domain.
Action
Find ContactsReturns SigParser contacts matching an email address or company domain.
Action
Find EmailsReturns distinct emails SigParser found across your mailboxes, filtered by email address or domain.
Action
Find MeetingsReturns distinct meetings SigParser found across your calendars, filtered by attendee, domain or date range.
Action
Upsert ContactCreates a contact in SigParser, or updates the existing contact with the same email address.
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 Digimon InformationThe Digimon API is a public reference catalogue of creatures from the Digimon franchise.
Pipefile to DisifyDisify checks email addresses for disposable and temporary providers.
Pipefile to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
More into SigParser
HubSpot to SigParserHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SigParserSalesforce is a leading enterprise customer relationship management (CRM) platform.
Google Sheets to SigParserGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to SigParserGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SigParserGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to SigParserGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Questions
Pipefile and SigParser, 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 SigParser when something happens in Pipefile?
Any of SigParser's 5 actions, including Find Companies, Find Contacts, Find Emails and Find Meetings. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from SigParser to Pipefile?
Yes. When something happens in SigParser, your agent can act in Pipefile too. This page covers both directions: SigParser's triggers and Pipefile's actions are listed here as well.
Do I have to build a connector for Pipefile or SigParser?
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 SigParser 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.