Actions4
- Rules Actions
- Accounts Actions
- Callbacks Actions
Overview
This node integrates with the Sequence API, specifically supporting the "Callbacks" resource and the operation POST /remote-api/amount. It allows users to send callback requests to the Sequence remote API endpoint related to amounts. This can be useful in scenarios where you need to notify or update external systems about amount-related events or trigger workflows based on such callbacks.
Practical examples include:
- Sending a callback to update payment or transaction amounts in an external accounting system.
- Triggering downstream processes when certain amount thresholds are reached or updated.
- Integrating Sequence's event-driven architecture with other services by forwarding amount-related callbacks.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose which credentials to use for authentication: - Sequence Rule API Secret (Rules): Used for Rules endpoints, authenticates via a signature header. - Sequence Access Token (Accounts): Used for Accounts endpoints, authenticates via an access token header. |
| x-sequence-signature (hidden) | Automatically managed header for authentication when using the Rule API Secret option. Contains the required signature for Rules endpoints. |
| x-sequence-access-token (hidden) | Automatically managed header for authentication when using the Access Token option. Contains the access token for Accounts endpoints. |
The hidden authentication headers are handled internally by the node and do not require manual input.
Output
The node outputs JSON data corresponding to the response from the Sequence API after making the POST request to /remote-api/amount. The structure of this JSON output depends on the API response but generally includes confirmation or details about the callback processed.
No binary data output is indicated for this operation.
Dependencies
- Requires an active internet connection to reach the Sequence API at
https://api.getsequence.io. - Requires one of two types of credentials:
- An API secret key credential for Rules endpoints (used as a signature header).
- An access token credential for Accounts endpoints.
- The node automatically manages the appropriate authentication headers based on the selected credential type.
- No additional environment variables or configurations are explicitly required beyond providing valid credentials.
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 not expired.
- Invalid endpoint or payload: Ensure that the operation matches the intended API endpoint (
POST /remote-api/amount) and that any required body parameters (if applicable) conform to the API specification. - Network issues: Connection timeouts or DNS errors may indicate network problems; check connectivity to
api.getsequence.io. - Empty or unexpected responses: Confirm that the API is returning expected data and that the node’s input parameters are correctly set.
Links and References
- Sequence API Documentation — Official documentation for the Sequence API.
- Sequence Authentication Guide — Details on how to obtain and use API secrets and access tokens.
- n8n HTTP Request Node — For understanding how n8n handles HTTP requests and authentication headers.