What you can do
Connect to 300+ connectors for collaboration, service management, and productivity (e.g., Slack, Microsoft Teams, Google Sheets, Gmail, Salesforce, Outlook, Microsoft Power BI, HTTP/Webhooks).
Automate actions across systems without writing a single line of code.
Test, monitor, and manage integrations directly in Pipefy, with detailed logs and flow traceability.
How it works (flow model)
Each flow is made of a trigger and actions.
🔹 Trigger
To start flows based on Pipefy events, use the official Pipefy connector configured with a Service Account that has access to the target pipe.
Supported card triggers include:
Card created
Card deleted
Card done
Card expired
Card field updated
Card late
Card moved
Card overdue
Card comment created
These triggers allow you to integrate with external systems whenever cards are created, updated, or moved, making your processes faster and more connected.
🔹 Actions
After the trigger, add steps such as:
Spreadsheets: create or update rows in Google Sheets for capacity and SLA reports.
Notifications: alert teams and channels in Slack or Microsoft Teams when a card changes phase or reaches a deadline.
Analytics: send data to Power BI to visualize performance, request volume, and average resolution times.
CRM/ERP: create new leads in Salesforce or retrieve information from NetSuite to enrich card details.
Direct integrations: use HTTP/Webhooks to connect with internal systems, ERPs, or data providers such as Big Data Corp, Serasa Experian, Boa Vista, ClearSale, or Neoway, enabling broader data cross-checking and automated external validations.
Why centralize in Pipefy’s iPaaS
Governance: authentication via Service Accounts with per-pipe permissions.
Security: scoped execution within Pipefy’s environment.
Scalability: manage multiple flows, environments, and connectors efficiently.
Operational simplicity: build, test, and monitor integrations where you already manage your processes.
Best practices
Use dedicated Service Accounts per context (e.g., by area or pipe) for better auditability and credential management.
Organize flows with consistent naming and folder structures by business domain.
Document HTTP/Webhook integrations when no connector is available, ensuring standardization and traceability.
Next steps
Set up a Service Account with access to your pipe.
Create your first flow (e.g., card created, moved, done, or updated).
Explore available connectors to extend your processes and automate more efficiently.