Chainstream Trigger icon

Chainstream Trigger

Handle Chainstream events via webhooks

Overview

This node acts as a webhook trigger for Chainstream events, allowing workflows to respond automatically when specific Chainstream events occur. It is particularly useful for integrating Chainstream event notifications into automation pipelines without polling. For example, it can trigger a workflow when a token migration event happens, enabling subsequent processing such as updating databases or notifying users.

Properties

Name Meaning
Authentication Method of authentication; currently supports "API Key" authentication.
Trigger On The specific Chainstream event topic to listen for. Currently supports "Token Migrated".
Filter A string filter to limit events to those matching the filter criteria (free text input).

Output

The node outputs JSON data representing the webhook event payload received from Chainstream. The output structure corresponds directly to the event's JSON body. No binary data output is produced.

Example output JSON structure:

[
  {
    /* Event data fields as sent by Chainstream */
  }
]

Dependencies

  • Requires an API key credential for authenticating requests and verifying webhook signatures.
  • Uses Chainstream's REST API to manage webhook registration.
  • Requires the node to be configured with a publicly accessible webhook URL to receive events.

Troubleshooting

  • Signature Verification Failure: If the incoming webhook request's HMAC signature does not match the expected value, the node will ignore the event. Ensure the API key (shared secret) is correctly configured and matches the one used in Chainstream.
  • Webhook Not Registered: The node attempts to register the webhook on activation. If registration fails, verify network connectivity and API key permissions.
  • Event Topic Mismatch: Events with topics different from the selected "Trigger On" property are ignored.
  • Filter Usage: The filter property is defined but not actively applied in the code; users should ensure filtering logic is handled downstream if needed.

Links and References

Discussion