Sequence

Interact with Sequence API
Join our community

Actions4

Overview

This node integrates with the Sequence API, specifically allowing users to create new accounts via the POST /accounts endpoint. It is useful in scenarios where automation workflows need to programmatically manage user accounts or integrate account creation into larger processes, such as onboarding flows or CRM synchronization.

For example, a marketing automation workflow could use this node to automatically create a new user account in Sequence when a lead fills out a form on a website.

Properties

Name Meaning
Authentication Choose which credentials to use:
- Sequence Rule API Secret (Rules): for Rules endpoints (uses x-sequence-signature header)
- Sequence Access Token (Accounts): for Accounts endpoints (uses x-sequence-access-token header)
Auth Header (managed by credentials) This hidden property is automatically managed by the node based on the selected authentication method. It sets the appropriate authorization header (x-sequence-signature or x-sequence-access-token) required by the API.

Note: The actual request body for creating an account is empty ({}) by default and handled internally.

Output

The node outputs JSON data representing the response from the Sequence API after creating an account. This typically includes details of the newly created account such as its ID and metadata returned by the API.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authentication:
    • Either a "Rule API Secret" for Rules endpoints (not applicable here),
    • Or an "Access Token" for Accounts endpoints (used here).
  • The node sends requests to the base URL: https://api.getsequence.io.
  • Proper configuration of these credentials within n8n is necessary for successful API calls.

Troubleshooting

  • Authentication errors: If the node returns unauthorized errors, verify that the correct credential type is selected and that the API key/token is valid and has the necessary permissions.
  • Empty or invalid responses: Ensure that the API endpoint is correct and that the Sequence service is operational.
  • Misconfigured headers: Since authorization headers are managed automatically, avoid manually overriding them to prevent conflicts.
  • Network issues: Check connectivity to api.getsequence.io.

Links and References

Discussion