Elevate Trigger icon

Elevate Trigger

Starts the workflow when Elevate notification events occur
Join our community

Overview

The Elevate Trigger node is designed to start an n8n workflow when specific notification events occur from the Elevate system. It acts as a webhook trigger, listening for incoming HTTP POST requests and filtering them based on selected event types. This node is particularly useful for automating processes in response to real-time updates or changes within the Elevate platform, such as user actions, document sharing, payout events, or quota updates.

Practical examples:

  • Automatically process payouts when a "Payouts Created" event is received.
  • Notify team members when a user's quota is updated.
  • Archive documents when a "Document Shared" event occurs.

Properties

Name Type Meaning
Events multiOptions The types of Elevate events that will trigger the workflow. Only selected events are processed.

Events options include:

  • Approval Updated
  • Quota Updated
  • Payouts Created
  • Payouts Deleted
  • Document Shared
  • Statements Frozen
  • User CRUD

Output

The node outputs a JSON object with the following structure:

[
  {
    "body": "<event type string or empty object>",
    "headers": { /* HTTP headers from the request */ },
    "query": { /* Full request body if matched, otherwise empty object */ }
  }
]
  • If the incoming event matches one of the selected "Events", body contains the event type (as a string), headers contains the HTTP headers, and query contains the full request body.
  • If the event does not match, all fields are empty objects except for headers.

Note: This node does not output binary data.

Dependencies

  • External Service: Requires Elevate to send HTTP POST notifications to the webhook URL generated by this node.
  • n8n Configuration: No special environment variables or API keys are required, but the webhook endpoint must be accessible to Elevate.

Troubleshooting

Common issues:

  • Webhook Not Triggering: Ensure the webhook URL is correctly configured in Elevate and is publicly accessible.
  • Event Not Processed: If the event type sent by Elevate does not exactly match any of the selected "Events", the workflow will not be triggered with meaningful data.
  • Empty Output: If no matching event is found, the output will contain empty objects. Double-check the event names and selection.

Error messages:

  • The node does not throw explicit error messages, but unexpected empty outputs usually indicate a mismatch between the incoming event and the selected "Events".

Links and References

Discussion