Cativa Trigger icon

Cativa Trigger

Start workflow when an event occurs

Actions3

Overview

The Cativa Trigger node for n8n is designed to start workflows when new users are detected in the Cativa system. It supports different strategies for fetching new user data, such as retrieving only users created since the last check, from a specific user ID, or all users. This node is particularly useful for automating onboarding processes, synchronizing user databases, or triggering notifications when new users join your platform.

Practical examples:

  • Automatically send a welcome email when a new user registers.
  • Sync new users with an external CRM or mailing list.
  • Trigger internal alerts or audits when a batch of new users is detected.

Properties

Name Meaning
Initial Data Determines how to fetch new users:
- From Now: Only users created after the workflow starts.
- From ID: Users after a given ID.
- All: All users, regardless of creation time.
From ID The specific user ID from which to start fetching new users. Only shown and required if "Initial Data" is set to "From ID".

Output

The output is a JSON array where each item represents a user object retrieved from Cativa. Each user object typically contains fields such as:

  • id: Unique identifier of the user.
  • shortId: An alternative short identifier (may include a guid property).
  • createdAt: Timestamp of when the user was created.
  • Other user-related properties as provided by the Cativa API.

Note: The exact structure of each user object depends on the Cativa API response, but you can expect standard user profile fields.

Dependencies

  • External Service: Requires access to the Cativa API.
  • Credentials: You must configure the cativaApi credential in n8n for authentication.
  • n8n Configuration: No special environment variables are needed beyond the credential setup.

Troubleshooting

Common Issues:

  • Authentication Errors: If credentials are incorrect or missing, the node will fail to connect to the Cativa API. Ensure the cativaApi credential is properly configured.
  • No New Users Detected: If the chosen fetch strategy does not match any new users (e.g., "From Now" but no users have been added since), the output may be empty.
  • Invalid "From ID": Providing a non-existent or malformed user ID in "From ID" mode may result in no users being fetched.

Error Messages:

  • "Authentication successful" / "Authentication failed": Indicates whether the provided credentials work.
  • API errors (e.g., network issues, permission denied) will be surfaced as error messages in the node execution log.

Links and References

Discussion