Sequence

Interact with Sequence API
Join our community

Actions4

Overview

This node allows triggering a specific rule in the Sequence platform by making a POST request to the /rules/{ruleId}/trigger endpoint. It is useful for automating workflows that depend on external events or conditions defined as rules within Sequence. For example, you might use this node to programmatically activate a notification rule when certain criteria are met in your system, or to trigger complex automation sequences managed by Sequence.

Properties

Name Meaning
Authentication Choose which credentials to use:
- Sequence Rule API Secret (Rules): Used for Rules endpoints with x-sequence-signature header.
- Sequence Access Token (Accounts): Used for Accounts endpoints with x-sequence-access-token header.
x-sequence-signature (hidden) Automatically managed authentication header for Rules endpoints when using the Rule API Secret credential.
x-sequence-access-token (hidden) Automatically managed authentication header for Accounts endpoints when using the Access Token credential.

Note: The hidden authentication headers are handled automatically by the node based on the selected Authentication option and do not require manual input.

Output

The node outputs JSON data representing the response from the Sequence API after triggering the specified rule. The exact structure depends on the API's response but typically includes confirmation of the trigger action or details about the triggered rule execution.

The node does not output binary data.

Dependencies

  • Requires an API key credential for authentication:
    • Either a Rule API Secret credential for Rules endpoints.
    • Or an Access Token credential for Accounts endpoints.
  • The node sends requests to the base URL: https://api.getsequence.io.
  • Proper configuration of these credentials in n8n is necessary for successful authentication.

Troubleshooting

  • Authentication errors: If the node returns unauthorized or forbidden errors, verify that the correct credential type is selected and that the API key or token is valid and has appropriate permissions.
  • Invalid rule ID: Ensure the ruleId parameter used in the path is correct and corresponds to an existing rule in your Sequence account.
  • Empty or malformed responses: Check network connectivity and confirm that the Sequence API service is operational.
  • Misconfigured authentication header: Since the authentication headers are managed automatically, avoid manually overriding them to prevent conflicts.

Links and References

Discussion