Integration
Connect Pipefile and Quilia
When File Request Created fires in Pipefile, your agent runs Create Contact in Quilia, or Appointment Created in Quilia 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 Quilia 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 Quilia can do together
From Pipefile to Quilia
When File Request Created in Pipefile
then Create Contact in Quilia
When File Request Created in Pipefile
then Update a Contact in Quilia
From Quilia to Pipefile
When Appointment Created in Quilia
then Create Contact in Pipefile
When Appointment Updated in Quilia
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 Quilia
Triggers and actions 4 triggers · 28 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
Appointment CreatedTriggers when a new appointment is created in Quilia.
Trigger
Appointment UpdatedTriggers when an appointment is updated in Quilia.
Trigger
New Client ActivityTriggers when a client performs an activity in Quilia, such as uploading a document to their case.
Action
Add New ClientCreates a new client in Quilia with their name, phone, email, address and date of birth.
Action
Create ContactCreates a contact (such as a witness, adjustor, employer or medical provider) attached to a case or a client.
Action
Delete a ContactPermanently deletes a company or people contact from your Quilia organization.
Action
Delete CasePermanently deletes a case, including its members, documents and chat history.
Action
Delete ClientPermanently deletes a client from your firm, including their case memberships.
Action
Delete DocumentsDeletes one or more Quilia documents, removing both the records and their stored files.
Action
Find a DocumentFinds a document by its id and returns its type plus a secure download link that expires after 30 minutes.
Action
Find Client by PhoneFinds a client in your firm by phone number and returns the client record with the cases they belong to.
Action
Invite Clients to CaseInvites clients or staff to a Quilia case. Clients are texted an invite; staff are added as invited. Returns who was invited and who was skipped.
Action
List ClientsReturns the firm's clients, optionally filtered by name, email or phone.
Action
List Webhook EventsReturns the webhook events your Quilia firm can subscribe to, with their descriptions and payload schemas.
Action
Retrieve a Single ClientReturns a single client by id, including the cases the client belongs to.
Action
Retrieve Individual CaseReturns one case by its ID, including its status, type, dates, client, organization and case members.
Action
Simulate Webhook EventSends a sample Quilia webhook event to an endpoint URL so you can test a webhook integration.
Action
Update a ContactUpdates an existing Quilia contact (a company or a person). Only the fields you fill in are changed.
Action
Update CaseUpdates an existing case's status, type, opening date or custom CMS data. Only the fields you fill in are changed.
Action
Update Client InformationUpdates an existing client's contact details, address and demographic information. Only the fields you fill in are changed.
Action
Upload DocumentsUploads a document file to a client's case in Quilia and returns the new document ids.
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 Quilia
HubSpot to QuiliaHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to QuiliaGoogle Sheets
Gmail to QuiliaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to QuiliaGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to QuiliaGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to QuiliaMailchimp marketing automation and email platform.
Questions
Pipefile and Quilia, 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 Quilia when something happens in Pipefile?
Any of Quilia's 18 actions, including Create Contact, Update a Contact, Update Case and Update Client Information. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Quilia to Pipefile?
Yes. When something happens in Quilia, your agent can act in Pipefile too. This page covers both directions: Quilia's triggers and Pipefile's actions are listed here as well.
Do I have to build a connector for Pipefile or Quilia?
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 Quilia 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.