Integration
Connect Pipefy and WordPress.com
When Moved Card fires in Pipefy, your agent runs Create Comment in WordPress.com, or New Comment in WordPress.com 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 WordPress.com to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Pipefy and WordPress.com can do together
From Pipefy to WordPress.com
When Moved Card in Pipefy
then Create Comment in WordPress.com
When New Card in Pipefy
then Create Page in WordPress.com
From WordPress.com to Pipefy
When New Comment in WordPress.com
then Create Record in Pipefy
When New Post in WordPress.com
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 WordPress.com
Triggers and actions 8 triggers · 32 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 CommentTriggers when a new approved comment is added to a post on your site.
Trigger
New PostTriggers when a new post is published on your site.
Action
Add mediaUploads one or more files to a WordPress.com site's media library from public URLs and returns the new media items.
Action
Create CategoryCreate a new category on a WordPress.com site.
Action
Create CommentCreate a new comment on a post on a WordPress.com site.
Action
Create PageCreate a new page on a WordPress.com site (a post with type=page).
Action
Create PostCreate a new post on a WordPress.com site. Status can be publish, draft, private, pending, or future.
Action
Create TagCreate a new tag on a WordPress.com site.
Action
Delete categoryDeletes a category from a WordPress.com site by its slug.
Action
Delete commentDeletes a comment on a WordPress.com site. The first delete moves it to the trash; deleting a trashed comment removes it permanently.
Action
Delete PostDelete (trash) a post on a WordPress.com site by post ID.
Action
Delete tagDeletes a tag from a WordPress.com site by its slug.
Action
Get commentReturns a single comment on a WordPress.com site, including its author, post, content and status.
Action
Get PostRetrieve a single post on a WordPress.com site by post ID.
Action
Get Site InfoRetrieve information about a WordPress.com site.
Action
List categoriesReturns the categories on a WordPress.com site, optionally filtered by a search term and sorted by name or post count.
Action
List CommentsList comments on a post on a WordPress.com site.
Action
List mediaReturns the items in a WordPress.com site's media library, optionally filtered by search text, file type, attached post or upload date.
Action
List PostsList posts on a WordPress.com site, optionally filtered by status, search term, or number to return.
Action
List tagsReturns the tags on a WordPress.com site, optionally filtered by a search term.
Action
List usersReturns the users of a WordPress.com site, optionally filtered by search text, role or capability.
Action
Update commentEdits an existing comment on a WordPress.com site — its text, author details, date or moderation status — and returns the updated comment.
Action
Update PostUpdate an existing post on a WordPress.com site by post ID.
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 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.
Pipefy to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Pipefy to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
More into WordPress.com
HubSpot to WordPress.comHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to WordPress.comSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to WordPress.comSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to WordPress.comGoogle Sheets
Gmail to WordPress.comGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to WordPress.comGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Pipefy and WordPress.com, 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 WordPress.com when something happens in Pipefy?
Any of WordPress.com's 21 actions, including Create Category, Create Comment, Create Page and Create Post. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from WordPress.com to Pipefy?
Yes. When something happens in WordPress.com, your agent can act in Pipefy too. This page covers both directions: WordPress.com's triggers and Pipefy's actions are listed here as well.
Do I have to build a connector for Pipefy or WordPress.com?
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.
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.