Sequence

Interact with Sequence API
Join our community

Actions4

Overview

This node allows triggering a specific rule in the Sequence platform via its remote API. It sends a POST request to the endpoint /remote-api/rules/{ruleId}/trigger, where {ruleId} is the identifier of the rule you want to activate. This operation is useful for automating workflows that depend on external events or conditions defined as rules in Sequence.

Typical use cases include:

  • Programmatically triggering notification rules when certain criteria are met.
  • Integrating Sequence rules into broader automation pipelines.
  • Testing or manually activating rules without using the Sequence UI.

Properties

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

The hidden authentication headers are handled internally by the node based on the selected authentication method and do not require manual input.

Output

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

No binary data output is involved in this operation.

Dependencies

  • Requires an active internet connection to reach https://api.getsequence.io.
  • Requires valid credentials:
    • Either a Rule API Secret credential for authenticating Rules endpoints.
    • Or an Access Token credential for Accounts endpoints (not applicable here since this operation targets Rules).
  • The node automatically sets appropriate HTTP headers for authentication based on the chosen credential type.

Troubleshooting

  • Authentication errors: If the node returns unauthorized or forbidden errors, verify that the correct credential type is selected and that the API secret or access token is valid and has sufficient permissions.
  • Invalid rule ID: Ensure the ruleId path parameter is correctly specified and corresponds to an existing rule in your Sequence account.
  • Network issues: Check your network connectivity and firewall settings if the node cannot reach the Sequence API endpoint.
  • Empty or unexpected responses: Confirm that the rule is configured properly in Sequence and that triggering it via API is supported.

Links and References

Discussion