Getting started with Pipefy Connector

Custom integrations are available for Enterprise Clients using Workato. Here are the basics you need to know.

G
Written by Guilherme Leme
Updated over a week ago

Estimated reading time: 4 minutes

Pipefy's Enterprise clients can count on custom integrations to attend to on-demand and specific needs.

Use Pipefy Connector to connect Pipefy to any other software, such as Salesforce, DocuSign, or Google Sheets (just to name a few).

We use an iPaaS (Integration as a Service) called Workato to make this connection. On Workato, integrations happen through connectors that execute the communication between two or more different systems once plugged in.

With Workato, we can integrate Pipefy into different systems, like SAP, Oracle, NetSuite, and MS Dynamics. But there are some considerations related to these types of integrations:

  • Usually, there are configurations to perform inside the ERP system, so your IT team must be onboard and available to configure part of the integration.

  • For SAP On-premise, the connector we have available in Workato is a Custom action Connector. This means we don't have pre-built actions or triggers; all integrations must be coded from scratch.

  • Some ERPs are hosted On-premise (inside a physical server). In these cases, an On-premise agent is necessary. Each on-premise agent setup has an additional annual fee and is only available for enterprise customers.

  • The On-Premise Agent provides a secure way to connect to on-premise applications, databases, and files using a TLS websocket tunnel.

Currently, our Solutions Design team makes this connection for our Enterprise clients.

How does Workato operate?

Workato operates according to a trigger → action logic, such as when a card is created in a pipe on Pipefy (trigger), another card is automatically created/updated in a 3rd party system (action).

Let's learn more about Pipefy Triggers and Pipefy Actions on Workato.

Pipefy Triggers

Pipefy provides a list of triggers to listen to events that happen in Pipes and Databases where you can configure integration with other systems when these events occur.

The list of triggers that Pipefy Connector provides for Pipes are:

  • New card - Triggers immediately when a card is created

  • Updated card - Triggers immediately when a card is updated

  • Moved card - Triggers immediately when a card is moved

  • Card expired - Triggers immediately when a card expires

  • Card late - Triggers immediately when a card is late

  • Card done - Triggers immediately when a card is done

  • Card overdue - Triggers immediately when a card is overdue

  • Deleted card - Triggers immediately when a card is deleted

The list of triggers related to Databases are:

  • New record - Triggers immediately when a record is created

  • Updated record - Triggers immediately when a record is updated

  • Record done - Triggers immediately when a record is done

  • Record overdue - Triggers immediately when a record is overdue

Pipefy Actions

Pipefy provides a list of actions to manage data in Pipefy when a 3rd party system, or even Pipefy, triggers an event.

With the actions, you can accomplish several tasks in pipes and databases you have access to in your Pipefy Organization.

The list of actions that Pipefy Connector provides for Pipes are:

  • Create card - Create a card in Pipefy

  • Delete card - Delete any card in Pipefy

  • Move card - Move a card to another phase in Pipefy

  • Update card - Update any card in Pipefy

  • Get cards by title - Get cards by title in Pipefy

  • Get cards by phase - Retrieve a list of cards that matches with the selected pipe phase

  • Get cards by field - Retrieve cards by a field in Pipefy

The list of actions that Pipefy Connector provides for Databases are:

  • Create record - Create a Database record in Pipefy

  • Delete record - Delete any Database record in Pipefy

  • Update record - Update any Database record in Pipefy

  • Get records - Retrieve Database records in Pipefy

  • Get records by field - Retrieve Database records by field in Pipefy

Keep learning about Pipefy Connector:

Did this answer your question?