Integration
Connect Pipefy and Zuddl
When Moved Card fires in Pipefy, your agent runs Create Event in Zuddl, or New Registration in Zuddl 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 Zuddl 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 Zuddl can do together
From Pipefy to Zuddl
When Moved Card in Pipefy
then Create Event in Zuddl
From Zuddl to 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 Zuddl
Triggers and actions 7 triggers · 43 actions
- Done Card
Triggers when a card is done.
- Moved Card
Triggers when a card is moved.
- New Card
Triggers when a new card is created.
- New Database Record
Triggers when a new record is created.
- Updated Card Field
Triggers when a card field is updated.
- Updated Record Field
Triggers when a record field is updated.
- Create Card
Creates a card in a Pipefy pipe, filling in its start form fields.
- Create Record
Creates a new table record.
- Delete Card
Permanently deletes a card from its pipe.
- Delete Database Record
Delete a database table record by ID via the GraphQL `deleteTableRecord(input: {id})` mutation.
- Find Card
Returns the cards in a pipe whose chosen field matches the specified value.
- Find Database Records
Find a database records by title.
- Get Card
Retrieves a single Pipefy card by its id, including its phase, pipe, assignees, labels, attachments and field values.
- Get Database Record
Fetch a single database table record by ID via the GraphQL `table_record(id: ID)` query.
- Move Card
Moves a Pipefy card to another phase of its pipe.
- Update Card Field
Sets a new value on one field of an existing Pipefy card.
- Update Database Record
Update a database table record's title/fields via the GraphQL `updateTableRecord(input: {id, title})` mutation.
- New Registration
Triggers when a new attendee registers for a Zuddl event or webinar.
- Add Attendee
Registers a new attendee for a Zuddl event.
- Approve Attendee Registration
Approves a pending attendee registration request.
- Create Event
Creates a new Zuddl event, webinar or field event.
- Create Location
Creates a location in a Zuddl event.
- Create Session
Creates a session in a Zuddl event.
- Create Speaker
Adds a new speaker to a Zuddl event.
- Create Sponsor
Adds a sponsor to a Zuddl event.
- Delete Location
Deletes a location from a Zuddl event.
- Get Attendee
Returns one attendee registration of a Zuddl event.
- Get Event
Returns the details of one Zuddl event.
- Get Location
Returns one location of a Zuddl event.
- Get Session
Returns one session of a Zuddl event.
- Get Speaker
Returns one speaker of a Zuddl event.
- Get Sponsor
Returns one sponsor of a Zuddl event.
- List Attendees
Returns the attendees registered for a Zuddl event.
- List Event Languages
Returns the languages a Zuddl event can be published in.
- List Events
Returns the events, webinars and field events in your Zuddl organization.
- List Event Tags
Returns the event tags defined in your Zuddl organization.
- List Locations
Returns the locations of a Zuddl event.
- List Sessions
Returns the sessions of a Zuddl event.
- List Speakers
Returns the speakers of a Zuddl event.
- List Sponsors
Returns the sponsors of a Zuddl event.
- List Teams
Returns the teams in your Zuddl organization you can create events in.
- Record Event Check-In
Checks an attendee into an event by their QR code.
- Record Event Check-Out
Checks an attendee out of an event by their QR code.
- Record Session Check-In
Checks an attendee into a session by their QR code.
- Record Session Check-Out
Checks an attendee out of a session by their QR code.
- Reject Attendee Registration
Rejects a pending attendee registration request.
- Update Location
Updates an existing location in a Zuddl event.
- Update Session
Updates an existing session in a Zuddl event.
- Update Speaker
Updates an existing speaker in a Zuddl event.
- Update Sponsor
Updates the supplied fields of a sponsor in a Zuddl event.
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 Zuddl
HubSpot to ZuddlHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to ZuddlSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to ZuddlSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to ZuddlGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to ZuddlGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ZuddlGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Pipefy and Zuddl, 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 Zuddl when something happens in Pipefy?
Any of Zuddl's 32 actions, including Create Event, Create Location, Create Session and Create Speaker. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Zuddl to Pipefy?
Yes. When something happens in Zuddl, your agent can act in Pipefy too. This page covers both directions: Zuddl's triggers and Pipefy's actions are listed here as well.
Do I have to build a connector for Pipefy or Zuddl?
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 Zuddl 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.