Orgo Trigger icon

Orgo Trigger

Starts the workflow when Orgo events occur (webhooks)

Overview

This node acts as a webhook trigger for Orgo events, starting an n8n workflow whenever specific events occur in the Orgo system. It listens for various event types such as contact creation, deletion, updates, event registrations, role assignments/removals, and user creation or updates.

Common scenarios where this node is beneficial include:

  • Automating follow-up actions when new contacts are added or updated.
  • Tracking event registrations and attendance changes to update CRM or marketing tools.
  • Managing user roles dynamically by triggering workflows on role assignment or removal.
  • Synchronizing user data across systems when users are created or updated.

For example, you could use this node to start a workflow that sends a welcome email when a new user registers or to update a mailing list when a contact's information changes.

Properties

Name Meaning
Events Select one or more Orgo event types that will trigger the webhook. Options include:
- [Contact] Created
- [Contact] Deleted
- [Contact] Updated
- [Event] Registration Created
- [Event] Registration Updated
- [Role] Assigned
- [Role] Removed
- [User] Created
- [User] Updated
Verify Signature Boolean flag to enable or disable verification of webhook signatures for security (recommended).
Options Collection of additional settings:
- Max Retries Maximum number of retry attempts for failed webhook deliveries (0 to 10, default 3).
- Timeout (Seconds) Timeout duration in seconds for webhook HTTP requests (1 to 300, default 30).

Output

The node outputs JSON data representing the received webhook payload from Orgo. The structure includes:

  • id: Unique identifier of the event.
  • event: Event type string.
  • api_version: API version of the event.
  • created: Timestamp of event creation.
  • tenant_id: Identifier of the tenant.
  • request: Request metadata.
  • object: The main object related to the event.
  • previous_attributes: Previous state attributes if applicable (nullable).
  • is_update: Boolean indicating if the event is an update.
  • entity_type: Type of entity involved.
  • operation: Operation performed.
  • _raw: The raw full webhook payload as received.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Orgo API.
  • The node uses the Orgo API URL and token from the configured credentials.
  • Webhook secret from credentials is used to verify incoming webhook signatures if enabled.
  • No external libraries beyond standard n8n workflow helpers are required.

Troubleshooting

  • Webhook signature missing: If signature verification is enabled but the incoming request lacks the expected signature header, the node will throw an error. Ensure that Orgo is configured to send the signature header.
  • Invalid webhook signature: Occurs if the signature does not match the computed hash using the webhook secret. Check that the webhook secret in credentials matches the one configured in Orgo.
  • Invalid Orgo webhook payload structure: Thrown if the payload lacks required fields (id, event, or object). Verify that Orgo sends the correct payload format.
  • Failed to create Orgo webhook: Happens during webhook registration if the API call fails. Confirm API credentials and network connectivity.
  • Webhook not triggering: Ensure that the selected events in the node match those configured in Orgo and that the webhook URL is correctly registered.

Links and References

Discussion