Cativa Trigger icon

Cativa Trigger

Start workflow when an event occurs

Actions3

Overview

The Cativa Trigger node is designed to start an n8n workflow when a new event occurs in the Cativa system. It supports polling for new users or groups, and can fetch initial data based on different strategies: from the current moment, from a specific ID, or all available data. This node is useful for automating processes that need to react to changes or additions in user or group data within Cativa.

Common scenarios:

  • Automatically processing new users as they are added to Cativa.
  • Syncing group information with other systems whenever a new group is created.
  • Migrating or auditing all existing users or groups by fetching all records.

Practical examples:

  • Triggering a welcome email workflow for every new user.
  • Notifying administrators when a new group is created.
  • Periodically syncing all user data to an external CRM.

Properties

Name Meaning
Initial Data Determines how the node fetches initial data:
- From Now: Only fetch items created after the workflow starts.
- From ID: Start fetching from a specific item ID (requires "From ID" value).
- All: Fetch all available items.
From ID The specific ID from which to start fetching data. Only required and visible if "Initial Data" is set to "From ID".

Output

The node outputs an array of JSON objects, each representing a user or group item retrieved from Cativa. The structure of each object depends on the resource type (user or group) but typically includes fields such as:

  • id
  • shortId (with possible subfields like guid)
  • createdAt
  • Other relevant user or group properties

If multiple items are found, the output will be an array of these objects, ordered from oldest to newest.

Note: The node does not output binary data.

Dependencies

  • External Service: Requires access to the Cativa API.
  • API Key/Credentials: Needs valid Cativa API credentials configured in n8n under the name cativaApi.
  • n8n Configuration: No special environment variables beyond standard 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 set up.
  • No data returned: If "From ID" is specified incorrectly or there are no new items since the last poll, the node may return an empty array or null.
  • Rate limits or API errors: If the Cativa API enforces rate limits or is unavailable, the node may throw errors indicating request failures.

Error messages and resolutions:

  • "Authentication failed" or similar: Check your API credentials.
  • "Cannot read property 'id' of undefined": Likely due to unexpected API response; verify that the resource and operation are correct and that the API is returning expected data.
  • "Request failed with status code XXX": Indicates an HTTP error from the Cativa API; check network connectivity and API status.

Links and References

Discussion