N8N Tools - Pipefy Trigger icon

N8N Tools - Pipefy Trigger

Listen to Pipefy webhook events for real-time automation

Overview

This node listens to real-time webhook events from Pipefy, a workflow and process management platform. It enables automation workflows in n8n by triggering on specific Pipefy events related either to cards within pipes or records within tables.

Common scenarios include:

  • Automating notifications or follow-up actions when a card is created, updated, moved, or completed.
  • Syncing Pipefy table record changes with other systems like CRMs or databases.
  • Triggering downstream processes when comments or attachments are added to cards.
  • Filtering events based on custom conditions to react only to relevant changes.

Practical examples:

  • When a new card is created in a sales pipeline, automatically send a welcome email to the client.
  • When a table record is updated, update corresponding data in an external database.
  • When a card is marked as done, trigger a Slack notification to the team.

Properties

Name Meaning
Trigger On Choose whether to listen for Card Events (events related to cards in a pipe) or Table Record Events (events related to records in a table).
Pipe ID The ID of the Pipefy pipe to monitor for card-related events. Required if "Trigger On" is set to Card Events.
Table ID The ID of the Pipefy table to monitor for record-related events. Required if "Trigger On" is set to Table Record Events.
Events Select one or more specific events to trigger on. Options depend on the "Trigger On" selection:
- For Card Events: Created, Updated, Moved, Done, Deleted, Field Updated, Assignee Added/Removed, Comment Added, Attachment Added.
- For Table Record Events: Created, Updated, Deleted, Field Updated.
Webhook Name Optional name for the webhook. If not provided, it will be auto-generated.
Additional Options Collection of optional settings:
- Filter Condition: JSON string to filter incoming webhook events by matching fields.
- Include Headers: Whether to include HTTP headers received in the webhook request.
- Custom Headers: Custom HTTP headers to include when creating the webhook.

Output

The node outputs JSON data representing the event payload with normalized fields depending on the event type:

  • For Card Events, output includes:

    • id: Card ID
    • title: Card title
    • eventType: Event type string (e.g., "card.created")
    • pipe: Object with pipe id and name
    • phase: Object with phase id and name
    • assignees: Array of assignees
    • labels: Array of labels
    • dueDate, done, createdAt, updatedAt, url
    • Additional fields depending on event type such as previousPhase, changedFields, assigneeChange, comment, or attachment

  • For Table Record Events, output includes:

    • id: Record ID
    • title: Record title
    • eventType: Event type string (e.g., "table_record.created")
    • table: Object with table id and name
    • recordFields: Array of record fields
    • createdAt, updatedAt, url
    • changedFields if applicable

If configured, the node can also include the raw webhook headers in the output under webhookHeaders.

The node does not output binary data.

Dependencies

  • Requires valid credentials for:

    • An API key credential for the N8N Tools API to validate subscription and access rights.
    • An API authentication token credential for Pipefy (Personal Access Token) to create and manage webhooks via Pipefy's GraphQL API.

  • The node interacts with:

    • N8N Tools API for subscription validation.
    • Pipefy GraphQL API for webhook creation, deletion, and validation.

  • No additional environment variables are required beyond these credentials.

Troubleshooting

  • Invalid API Key or Subscription Issues
    Error messages like "N8N Tools API validation failed" or "Pipefy integration requires N8N Tools subscription" indicate problems with the N8N Tools API key or subscription plan.
    Resolution: Verify your API key at the N8N Tools dashboard and ensure your subscription plan supports Pipefy integrations.

  • Invalid Pipefy Credentials
    Errors mentioning invalid Pipefy credentials or Personal Access Token mean the Pipefy token is incorrect or expired.
    Resolution: Check and update your Pipefy personal access token.

  • API Rate Limits Exceeded
    If you receive errors about rate limits ("Pipefy API rate limit exceeded"), it means too many requests were made in a short time.
    Resolution: Reduce request frequency or wait before retrying.

  • Webhook Creation Failures
    Errors during webhook creation may occur due to invalid parameters or network issues.
    Resolution: Ensure required fields like Pipe ID or Table ID are correctly set and that the webhook URL is accessible.

  • No Trigger on Events
    If the node never triggers, verify that the selected events match those sent by Pipefy and that any filter condition is correct JSON and matches the event payload.

Links and References

Discussion