AIR Trigger icon

AIR Trigger

Trigger workflows based on AIR events

AIR Trigger

AI-generated

Overview

The AIR Trigger node is designed to trigger workflows based on specific AIR events received via webhooks. It listens for incoming POST requests containing event data, validates the authorization using a Bearer token, and filters events based on user-selected event types. This node is useful for automating workflows that need to respond to real-time events from the AIR platform, such as notifications, updates, or other event-driven actions.

Use Case Examples

  1. Trigger a workflow when a specific AIR event occurs, such as a new user registration or a system alert.
  2. Filter incoming AIR events to only process those relevant to the workflow, ignoring others.
  3. Secure webhook endpoints by validating incoming requests with a Bearer token.

Properties

Name Meaning
Event Names or IDs Specifies which AIR event types the node should listen for and trigger the workflow on. Users can select from a list or specify event IDs using expressions.
Bearer Token The Bearer token used to authenticate incoming webhook requests. The node checks this token against the Authorization header to ensure the request is authorized.

Output

JSON

  • json - The JSON payload of the received AIR event.
  • headers - The HTTP headers from the incoming webhook request.

Dependencies

  • Requires an API key credential for AIR API authentication to load event types.
  • Uses HTTP POST webhook to receive event data.

Troubleshooting

  • If the authorization header is missing or the Bearer token does not match, the node responds with a 401 Unauthorized error.
  • If the event payload does not contain a valid 'eventName' string, the node responds with a 400 Bad Request error.
  • If the received event is not in the selected event types, the event is ignored and the workflow is not triggered.
  • Ensure the Bearer token configured in the node matches the token sent by AIR in the webhook Authorization header.

Links

Discussion