Integration
Connect Pipefile to Flodesk
When File Request Created fires in Pipefile, your agent runs Find a Subscriber by Email Address in Flodesk. 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 Flodesk 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 can start in Flodesk
When File Request Created in Pipefile
then Find a Subscriber by Email Address in Flodesk
When File Request Created in Pipefile
then Add custom field in Flodesk
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 Flodesk
Triggers and actions 1 trigger · 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.
Action
Add custom fieldCreates a new subscriber custom field in your Flodesk account with the label you choose.
Action
Add Existing Subscriber to SegmentAdds an existing Flodesk subscriber to one or more segments and returns the updated subscriber.
Action
Add Existing Subscriber to WorkflowAdds an existing Flodesk subscriber to a workflow, identified by subscriber ID or email address.
Action
Add segmentCreates a new segment in your Flodesk account and returns it.
Action
Create/Update SubscriberCreates a new Flodesk subscriber, or updates the existing one with the same email address or id, optionally adding them to segments.
Action
Find a Subscriber by Email AddressLooks up a Flodesk subscriber by email address and returns their status, name, segments and custom field values.
Action
Get segmentReturns a single Flodesk segment, including its name, color, type and number of active subscribers.
Action
List campaignsReturns the email campaigns in your Flodesk account, optionally filtered by status or a search term.
Action
List custom fieldsReturns every subscriber custom field defined in your Flodesk account, with each field's key and display label.
Action
List segmentsReturns all segments in your Flodesk account, with each segment's name, color, type and active subscriber count.
Action
List subscribersReturns subscribers in your Flodesk account, optionally filtered by status or segment.
Action
List workflowsReturns the workflows in your Flodesk account, optionally filtered by status (active, paused or draft).
Action
Remove Existing Subscriber From SegmentRemoves an existing Flodesk subscriber from one or more segments and returns the updated subscriber.
Action
Remove Existing Subscriber From WorkflowRemoves an existing subscriber, identified by subscriber ID or email address, from a Flodesk workflow.
Action
Unsubscribe SubscriberUnsubscribes a subscriber from all of your Flodesk lists so they no longer receive marketing emails, and returns the updated subscriber.
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 Flodesk
HubSpot to FlodeskHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to FlodeskSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to FlodeskSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to FlodeskGoogle Sheets
Gmail to FlodeskGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to FlodeskGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Pipefile and Flodesk, 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 Flodesk when something happens in Pipefile?
Any of Flodesk's 15 actions, including Create/Update Subscriber, Add custom field, Add Existing Subscriber to Segment and Add Existing Subscriber to Workflow. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Flodesk to Pipefile?
Flodesk has no triggers in the catalog today, so automations start in Pipefile. If you need the other direction, ask: your agent reads Flodesk's API documentation and adds it.
Do I have to build a connector for Pipefile or Flodesk?
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 Flodesk 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.