Integration
Connect Pipefy and Storydoc
When Moved Card fires in Pipefy, your agent runs Find Analytics Events in Storydoc, or New Version in Storydoc to Create Record in Pipefy. 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 Pipefy and Storydoc 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 Pipefy and Storydoc can do together
From Pipefy to Storydoc
When Moved Card in Pipefy
then Find Analytics Events in Storydoc
When New Card in Pipefy
then Create a New Story Version in Storydoc
From Storydoc to Pipefy
When New Version in Storydoc
then Create Record in Pipefy
When New Version in Storydoc
then Update Database Record in Pipefy
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 Pipefy and Storydoc
Triggers and actions 7 triggers · 22 actions
Trigger
Done CardTriggers when a card is done.
Trigger
Moved CardTriggers when a card is moved.
Trigger
New CardTriggers when a new card is created.
Trigger
New Database RecordTriggers when a new record is created.
Trigger
Updated Card FieldTriggers when a card field is updated.
Trigger
Updated Record FieldTriggers when a record field is updated.
Action
Create CardCreates a card in a Pipefy pipe, filling in its start form fields.
Action
Create RecordCreates a new table record.
Action
Delete CardPermanently deletes a card from its pipe.
Action
Delete Database RecordDelete a database table record by ID via the GraphQL `deleteTableRecord(input: {id})` mutation.
Action
Find CardReturns the cards in a pipe whose chosen field matches the specified value.
Action
Find Database RecordsFind a database records by title.
Action
Get CardRetrieves a single Pipefy card by its id, including its phase, pipe, assignees, labels, attachments and field values.
Action
Get Database RecordFetch a single database table record by ID via the GraphQL `table_record(id: ID)` query.
Action
Move CardMoves a Pipefy card to another phase of its pipe.
Action
Update Card FieldSets a new value on one field of an existing Pipefy card.
Action
Update Database RecordUpdate a database table record's title/fields via the GraphQL `updateTableRecord(input: {id, title})` mutation.
Trigger
New VersionTriggers when a new personalized story version is created in your Storydoc account.
Action
Create a New Story VersionCreates a personalized version of a story template for a prospect and returns its share links.
Action
Find Analytics EventsReturns viewer analytics events (opens, clicks, accepts) for your stories within a date range.
Action
Generate StoryGenerates and publishes a new story from a text prompt, optionally branded for a company.
Action
Get AccountReturns your Storydoc organization's ID and name.
Action
Get StoryReturns one story template, including its dynamic variables.
Action
Get Story VariablesReturns the variables and repeatable content groups a story template accepts when creating a version.
Action
Get VersionReturns one personalized story version.
Action
List FoldersReturns the folders in your Storydoc organization.
Action
List StoriesReturns all story templates in your Storydoc account, optionally filtered by status.
Action
List VersionsReturns a page of personalized story versions, filterable by story, folder, sender, title and status.
Action
Update Story VersionUpdates the personalization data of an existing story version, keeping its manual edits.
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 Pipefy
Pipefy to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Pipefy to Hyrule CompendiumHyrule Compendium is an open-source REST service exposing data on every interactive item in The Legend of...
Pipefy to PublerPubler is a social media management platform that lets you plan, schedule, and analyze posts across multiple...
Pipefy to Spaceflight NewsSpaceflight News API aggregates news coverage of spaceflight and the space industry from many publishers.
Pipefy to SparrowDeskSparrowDesk is an AI-first helpdesk that unifies customer support across email & chat while automating...
Pipefy to TimingTiming is an automatic time tracking app for macOS.
More into Storydoc
HubSpot to StorydocHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to StorydocSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to StorydocSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to StorydocGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to StorydocGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to StorydocGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Pipefy and Storydoc, answered
What can start an automation from Pipefy?
Any of Pipefy's 6 triggers in the catalog, including Moved Card, New Card, New Database Record and Updated Card Field. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Storydoc when something happens in Pipefy?
Any of Storydoc's 11 actions, including Create a New Story Version, Update Story Version, Find Analytics Events and Generate Story. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Storydoc to Pipefy?
Yes. When something happens in Storydoc, your agent can act in Pipefy too. This page covers both directions: Storydoc's triggers and Pipefy's actions are listed here as well.
Do I have to build a connector for Pipefy or Storydoc?
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 Pipefy and Storydoc 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.