Skip to main content
Pipefy is a workflow management platform that helps teams automate and optimize business processes using customizable pipes, cards, and phases.

​
1. Add your Pipefy access

  1. In the Destinations tab, click on the “Add destination” button located on the top right of your screen. Then, select the Pipefy option from the list of connectors.
  2. Click Next and you’ll be prompted to add your access:
    • Access Token: Your Pipefy Personal Access Token or Service Account token. You can generate one from your Pipefy account settings under “Personal access tokens” or by creating a service account.
    • Endpoint: The operation to perform. Choose CreateCard to create new cards or UpdateCard to update existing ones.
    • Pipe ID: The ID of the Pipefy pipe where cards will be created or updated. You can find this in the pipe’s URL or settings.
    • Enable partial success: Whether the connector should continue trying to sync records after one fails.
  3. Click Next.

​
2. Select your data to send

  1. The next step is letting us know which data you want to send. Select the layer and then the desired table.
    Tip: The table can be found more easily by typing its name.
  2. Click Next.

​
3. Map your data fields

Configure how the fields from your source table should be mapped to the fields in the selected endpoint. Below you can find the supported fields for each endpoint.
This endpoint creates a new card in the specified pipe. Below are the fields you can map your data to:
FieldTypeRequiredDescription
titleStringNoThe title of the card.
due_dateDateTimeNoThe due date for the card.
phase_idStringNoThe ID of the phase to place the card in.
assignee_idsArray of StringsNoThe IDs of users to assign to the card.
label_idsArray of StringsNoThe IDs of labels to apply to the card.
Custom fieldsVariesNoAny other field ID maps to a custom pipe field. Use the field’s internal ID as the destination field name.
This endpoint updates an existing card. Card-level fields (title, due date, assignees, labels) are updated in a single request, while custom fields are updated individually. Below are the fields you can map your data to:
FieldTypeRequiredDescription
idStringYesThe ID of the card to update.
titleStringNoThe new title of the card.
due_dateDateTimeNoThe new due date for the card.
assignee_idsArray of StringsNoThe new list of assignee IDs.
label_idsArray of StringsNoThe new list of label IDs.
Custom fieldsVariesNoAny other field ID maps to a custom pipe field. Use the field’s internal ID as the destination field name.

​
4. Configure your Pipefy data destination

  1. Describe your destination for easy identification within your organization. You can inform things like what data it brings, to which team it belongs, etc.
  2. To define your Trigger, consider how frequently you need to have the data updated on the destination (every day, once a week, only at specific times, etc.).
  3. Click Done.

​
Check your new destination!

  1. Once completed, you’ll receive confirmation that your new destination is set up!
  2. You can view your new destination on the Destinations page. Now, for you to be able to see it on Pipefy, you have to wait for the pipeline to run. You can monitor it on the Destinations page to see its execution and completion. If needed, manually trigger the pipeline by clicking on the refresh icon. Once executed, your data should be seen on Pipefy.
If you encounter any issues, reach out to us via Slack, and we’ll gladly assist you!