Actionist·Pipefy
Pipefy

Pipefy

· #245 most-used

Run every business process from one no-code control plane

ProductivityProjectsDatabaseFormsAutomationNo-Code

Pipefy is an AI-powered no-code business process management platform that lets teams design, automate, and govern any workflow — from HR onboarding and procurement approvals to IT service requests and sales pipelines — without writing code. Connect it to Actionist and your agents can create cards on any pipe, move work through stages, update field values, query records in Pipefy's database tables, and react to pipeline events within about a minute of them happening — all without anyone touching the Pipefy interface.

Try Pipefy with ActionistVisit Pipefy
Average time saved
10 hours
per person · per month
≈ 1 workdays back

Eliminates manual work. Agents eliminate manual card creation, field updates, and status-check queries that currently require navigating the Pipefy interface multiple times per day across every team.

Schedule

What your Pipefy agent runs on autopilot

A week of scheduled jobs your Actionist agent will execute on your behalf.

28Scheduled jobs
7Agents at work
24/7Always on
Agents
Tue–Thu
Tue
Wed
Thu
7a
8a
9a
10a
11a
12p
1p
2p
3p
4p
5p
6p
Multi-app workflows

Pipefy × every other app you use

End-to-end automations that span multiple apps — each one a real business outcome.

6Workflows
7Apps spanned
~31 hrsSaved / week
6Personas served
For finance
Featured3 apps

Purchase request to approved PO without a single email

When an employee submits a purchase request form, the agent checks the vendor against the Pipefy supplier database, creates an intake card in the Procurement pipe with all fields populated, notifies the approver in Slack with the request details and a direct card link, moves the card to 'Approved for Payment' when the approver clicks confirm, and logs the approved PO to the finance tracking sheet in Google Sheets — the entire chain from submission to payment queue runs without a single email relay.

~10 hrs

Time saved for your team — every week, on autopilot

The flow
Trigger·When a purchase request form is submitted
Trigger
Step 1
Pipefy
Detect new purchase request form submission
read
Step 2
Pipefy
Find Database Records — check vendor in approved supplier list
write
Step 3
Pipefy
Create Card in Procurement pipe with vendor, amount, and cost centre
write
Step 4
Slack
Notify approver with card details and direct link
write
Step 5
Pipefy
Move Card to Approved phase when approver confirms
write
Step 6
Google Sheets
Log approved PO to finance tracking sheet
Result
Create Card in Procurement pipe with vendor, amount, and cost centreNotify approver with card details and direct linkMove Card to Approved phase when approver confirmsLog approved PO to finance tracking sheet
The win
Saved per run
40 min
Runs / week
~15×
Procurement cycles that took 3 days of email chains complete in under an hour
Driven byFinance Agent
ROI

Savings

What your team gets back — two angles: what you stop doing manually, and what that's worth.

Without Actionist

What you do manually today

With Actionist

What your agent runs for you

  • Sales
    25 min / week
    Manual deal card creation and field updates

    Sales reps open Pipefy after every CRM update to create or edit a deal card, re-entering the deal value, close date, and contact details that already exist in HubSpot — typically 10 minutes of duplication per deal per week.

    Sales Agent
    0 min
    Agent syncs CRM and Pipefy automatically

    When a deal changes in HubSpot, the agent updates the corresponding Pipefy card field within about a minute — reps never open Pipefy just to paste data they already entered elsewhere.

  • Marketing
    15 min / week
    Manual campaign card creation each sprint

    The marketing coordinator creates a Pipefy card for each campaign manually at the start of every sprint — pulling details from the content calendar, filling in channel, launch date, and owner one at a time.

    Marketing Agent
    0 min
    Agent creates campaign cards from the content calendar

    When a new campaign is added to the content calendar in Notion, the agent creates the Pipefy card with all fields pre-populated within about a minute — the coordinator's Monday morning card-creation routine disappears.

  • Customer Support
    30 min / week
    Manual SLA monitoring and escalation emails

    Team leads scan open ticket cards in Pipefy every morning to identify SLA risks, then manually send Slack messages or emails to assignees — a daily sweep that takes 20 to 30 minutes and still misses cards that breach overnight.

    Customer Support Agent
    0 min
    Agent escalates overdue and late cards automatically

    The agent fires within about a minute of a card entering the late or overdue state, posting a Slack escalation and adding a comment to the card — breaches surface immediately without a morning sweep.

  • Human Resources
    20 min / week
    Manual onboarding card creation per new hire

    The HR coordinator creates a Pipefy onboarding card for each new hire by hand, pulling details from the HRIS and filling in 8-10 fields — a 15-minute task per hire that happens in a rush on the employee's first day.

    Human Resources Agent
    0 min
    Agent creates onboarding cards from HRIS data before start day

    When a hire is confirmed in the HRIS, the agent creates the Pipefy card with all fields populated and notifies IT and Facilities — the onboarding card exists days before the employee arrives.

  • Finance
    20 min / week
    Manual vendor eligibility checks before approvals

    Before approving a purchase request, the AP team manually looks up the vendor in the supplier database to verify compliance status — a 5-minute search per PO that blocks the approval queue when the person doing it is unavailable.

    Finance Agent
    0 min
    Agent checks vendor eligibility before creating the PO card

    The agent queries the Pipefy vendor database before creating a procurement card and flags any unregistered or suspended vendor in the card's comment — no PO card reaches the approval queue without a vendor check.

  • Operations
    90 min / week
    Manual weekly operations report from Pipefy data

    An operations analyst spends 60-90 minutes every Monday navigating each pipe, counting cards in each phase, and pasting the numbers into a Google Sheet before the leadership standup — the report is often incomplete or late.

    Operations Agent
    0 min
    Agent builds the weekly operations report automatically

    The Operations Agent queries all pipes, calculates throughput and cycle times, and posts a complete health summary to Slack and Google Sheets before 7 AM every Monday — the report is always ready, always complete.

  • Legal
    30 min / week
    Manual contract expiry tracking in spreadsheets

    The legal team maintains a separate spreadsheet of contract expiry dates, manually checking it each week to identify renewals due in the next 60 days — a task that gets skipped under deadline pressure with expensive consequences.

    Legal Agent
    0 min
    Agent creates renewal cards 60 days before every contract expires

    The agent queries the Contracts database weekly, finds all contracts expiring within 60 days, and creates renewal cards in Pipefy automatically — the legal team never discovers an expired contract by accident.

+ 100s of other Pipefy automations
Average time saved
23 hrs / person / month
Calculator

Calculate what your team saves

Team size
5 people
Hourly rate
$75 / hr
Hours saved / week
13
Hours saved / year
625
Annual ROI
$46,875

Based on Pipefy's typical team usage — the visible tasks plus a few other automations the agent runs: ~2.5 hrs / person / week of admin work automated.

Connect

How to plug Pipefy into Actionist

Pick the connection method that suits your environment.

The standard path to Pipefy. Generate a personal access token in your Pipefy account settings and paste it into Actionist — the agent authenticates every GraphQL call with that token.

1
Open Personal Access Tokens

In Pipefy, click your avatar → Account Settings → Personal Access Tokens. Click Generate new token, give it a descriptive name (e.g. 'Actionist'), and copy the value.

2
Paste into Actionist

Find Pipefy in the Apps library, click Connect, and paste your token into the API token field.

3
Test the connection

Actionist runs a lightweight read query to verify the token. A green checkmark confirms the handshake.

Credentials you'll need
API token*
Pipefy → Account Settings → Personal Access Tokens → Generate token
Actions

12 actions your agent can call

Read and write operations available to your Actionist agent.

Triggers

9 events your agent can react to

Events your agent watches for, and the actions it kicks off in response.

FAQs

Questions about Pipefy + Actionist

How does Actionist connect to Pipefy?
Go to the Apps tab, find Pipefy, and click Connect. You will need a Pipefy Personal Access Token — generate one in your Pipefy account settings under Personal Access Tokens. Paste the token into the API token field in Actionist and click Test connection. Actionist runs a lightweight read query to verify the token is valid before allowing any actions to run. The token inherits the permissions of the user who generated it, so use a token from an account that has access to the pipes and databases your agent needs.
What permissions does the agent need on my Pipefy account?
Actionist uses Pipefy's GraphQL API, which authenticates via a Personal Access Token tied to a specific user account. The agent can only access pipes, cards, and databases that the token-generating user can access in Pipefy. For read actions (Find Card, Find Database Records, List Cards in Phase, Get Card Details), the user needs at least Member access on the relevant pipe. For write actions (Create Card, Move Card, Update Card Field), they need Member or Admin access. For database operations, the user needs access to the relevant table. Actionist does not modify your Pipefy permission settings — those are controlled from within Pipefy itself.
Can I use Pipefy triggers to start workflows in other apps?
Yes — Pipefy's webhook-based triggers in Actionist fire within about a minute of the event occurring in Pipefy. Available triggers include New Card (any new card created in a pipe), Moved Card (when a card changes phase), Done Card (when a card reaches the final phase), Updated Card Field (when a specific field value changes), Overdue Card, Late Card, Expired Card, New Database Record, and Updated Record Field. Each trigger delivers the card or record data to downstream steps so your agent can update a CRM, send a Slack message, create a calendar invite, or run any other action across Actionist's 200+ connected apps.
How do I avoid creating duplicate cards when the same request comes from multiple sources?
Use Find or Create Card instead of Create Card when the same request might arrive through more than one channel. This action searches the specified pipe for an existing card matching your criteria (usually a title or a unique field value like an email or order number) and returns it if found, only creating a new card when no match exists. This keeps your pipes clean even when intake comes from forms, emails, and CRM systems simultaneously. If you need an exact match on a specific field value rather than the title, use Find Card first, then branch on whether a result was returned before deciding to create.
What is the difference between Pipefy pipes and Pipefy database tables?
Pipes are Pipefy's workflow engine — a card moves through sequential phases (like 'New → In Progress → Done'), capturing process history and enabling automation at each stage transition. Database tables are Pipefy's structured data layer — they hold reference data like vendor records, employee details, or budget allocations that do not follow a workflow but need to be queried and updated. In Actionist, card actions (Create Card, Move Card, Find Card) target pipes, while record actions (Create Record, Find Database Records) target database tables. A common pattern is to query a database table to validate or enrich data before creating or updating a pipe card.
Can Actionist work with multiple Pipefy pipes in the same agent or workflow?
Yes — a single Actionist agent or workflow can interact with as many Pipefy pipes and database tables as needed. You specify the target pipe by ID or name on each action step, so one workflow can create a card in the Procurement pipe, look up a record in the Vendor database table, and move a card in the Legal pipe — all in sequence. This makes cross-departmental handoffs (for example, a sales close that triggers both a Pipefy onboarding card and a Pipefy legal card) straightforward to automate without building separate workflows per pipe.
How does the Overdue Card trigger differ from the Late Card trigger?
In Pipefy, a card becomes 'late' when it has been in its current phase longer than the maximum time configured for that phase's SLA, but it has not yet passed the card's overall due date. It becomes 'overdue' when the card's due date has passed without reaching Done. The Late Card trigger fires first and gives you a proactive warning window — ideal for sending a reminder to the assignee or alerting a manager. The Overdue Card trigger fires when the breach has actually occurred, making it suited for escalation actions like creating a formal breach record or notifying the customer. Using both triggers lets you build a two-stage response: warn early, escalate on breach.
Does Actionist support Pipefy's no-code automation rules alongside AI agents?
Yes — Actionist agents and Pipefy's native no-code automation rules run independently and complement each other. Pipefy's built-in automations (conditional moves, email sends, field updates triggered by phase entry) continue working exactly as configured. Actionist agents extend the automation surface by connecting Pipefy to external systems — CRMs, finance tools, communication platforms, and data stores — in ways that Pipefy's native automations cannot reach. You do not need to replace your existing Pipefy automations to use Actionist; the two layers layer together cleanly.