Integration
Connect Flatfile and Pyrus
When New Agent fires in Flatfile, your agent runs Add Task Comment in Pyrus, or New Form Task in Pyrus to Create Document in Flatfile. 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 Flatfile and Pyrus 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 Flatfile and Pyrus can do together
From Flatfile to Pyrus
When New Agent in Flatfile
then Add Task Comment in Pyrus
When New App in Flatfile
then Find Form Tasks in Pyrus
From Pyrus to Flatfile
When New Form Task in Pyrus
then Create Document in Flatfile
When New Form Task in Pyrus
then Upload File in Flatfile
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 Flatfile and Pyrus
Triggers and actions 9 triggers · 15 actions
Trigger
New AgentTriggers when a new agent is created.
Trigger
New AppTriggers when a new app is created.
Trigger
New DocumentTriggers when a new document is created in a space.
Trigger
New EventTriggers when a new event occurs in Flatfile.
Trigger
New PromptTriggers when a new prompt is created.
Trigger
New SheetTrigger when a new sheet is created in a Flatfile workbook.
Trigger
New UserTriggers when a new user is created.
Trigger
New WorkbookTrigger when a new workbook is created in Flatfile.
Action
Create DocumentCreates a new document in Flatfile.
Action
Create PromptCreates a new AI prompt in Flatfile.
Action
Get DocumentRetrieves a single document from a Flatfile space by its ID.
Action
Upload FileUploads a file to Flatfile.
Trigger
New Form TaskTriggers when a new task is created from a Pyrus form.
Action
Add MemberAdds a user to the Pyrus organization.
Action
Add Task CommentAdds a comment to a Pyrus task, and can also close or reopen it, approve or reject it, or reassign it.
Action
Delete TaskDeletes a Pyrus task.
Action
Find Catalog ItemsReturns a Pyrus catalog's items, optionally only those whose column matches a value.
Action
Find Form TasksSearches the tasks created from a Pyrus form, by text, step, or creation and modification dates.
Action
Get FormReturns a Pyrus form template with its fields.
Action
Get MemberReturns a Pyrus organization member's profile by ID.
Action
Get TaskReturns a Pyrus task with its fields, participants and comments.
Action
List CatalogsReturns all Pyrus catalogs, without their items.
Action
List FormsReturns all Pyrus form templates the user manages or belongs to.
Action
List MembersReturns all members of the Pyrus organization.
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 Flatfile
Flatfile to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Flatfile to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Flatfile to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Flatfile to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Flatfile to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Flatfile to Google DriveGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
More into Pyrus
HubSpot to PyrusHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to PyrusGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to PyrusGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PyrusGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to PyrusGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to PyrusMailchimp marketing automation and email platform.
Questions
Flatfile and Pyrus, answered
What can start an automation from Flatfile?
Any of Flatfile's 8 triggers in the catalog, including New Agent, New App, New Document and New Event. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Pyrus when something happens in Flatfile?
Any of Pyrus's 11 actions, including Add Member, Add Task Comment, Find Catalog Items and Find Form Tasks. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Pyrus to Flatfile?
Yes. When something happens in Pyrus, your agent can act in Flatfile too. This page covers both directions: Pyrus's triggers and Flatfile's actions are listed here as well.
Do I have to build a connector for Flatfile or Pyrus?
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 Flatfile and Pyrus 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.