SwipeFlow Trigger icon

SwipeFlow Trigger

Listen for events in SwipeFlow
Join our community

Overview

This node acts as a trigger for events occurring in the SwipeFlow platform. It listens for specific project-related events such as item creation, updates, approvals, rejections, deletions, change requests, and project triggers. When one of these events occurs, the node captures the event data and triggers a workflow in n8n. This is useful for automating processes based on real-time changes in SwipeFlow projects, such as notifying teams of item status changes or initiating follow-up actions when a project event happens.

Use Case Examples

  1. Trigger a workflow when an item in a SwipeFlow project is approved to notify stakeholders.
  2. Start a process when a new item is created in a project to automatically assign tasks.
  3. Listen for project-level triggers to synchronize data with other systems.

Properties

Name Meaning
Project Name or ID Selects the SwipeFlow project to monitor for events. Can be chosen from a list or specified via an expression.
Events Specifies which item or project events to listen for, such as item approved, created, deleted, or project triggered.

Output

JSON

  • event - The type of event that triggered the webhook (e.g., item.created, item.approved).
  • timestamp - The timestamp when the event occurred.
  • item - The item data related to the event, including metadata if available.
  • decision - Decision data related to the item event, if applicable.
  • projectId - The ID of the project for project-level trigger events.
  • triggerName - The name of the project trigger event.
  • triggerEvent - The specific event that triggered the project-level webhook.
  • triggeredBy - Information about who or what triggered the project event.

Dependencies

  • SwipeFlow API

Troubleshooting

  • Ensure the project ID is correctly specified and accessible with the provided credentials.
  • Verify that the selected events are supported and correctly configured in SwipeFlow.
  • Check webhook URL accessibility and that the n8n instance is reachable from SwipeFlow.
  • Common errors include 'Invalid webhook payload' if the incoming data is malformed, and 'Unsupported event type' if an event outside the configured list is received. These can be resolved by validating the webhook setup and event configuration.

Links

Discussion