Cativa Trigger icon

Cativa Trigger

Start workflow when an event occurs

Actions3

Group → New Posts

AI-generated

Overview

The Cativa Trigger node for n8n is designed to start workflows when new posts are detected in a specified group. It periodically polls the Cativa API for new group posts, supporting different strategies for fetching data (from now, from a specific ID, or all available posts). This node is particularly useful for automating actions based on new content in groups, such as notifications, archiving, or further processing of group discussions.

Practical examples:

  • Automatically send a Slack message when a new post appears in a monitored group.
  • Archive new group posts to a database for compliance or analytics.
  • Trigger approval workflows when certain keywords appear in new group posts.

Properties

Name Meaning
Initial Data Determines how the node fetches initial posts:
- From Now: Only posts created after the workflow starts.
- From ID: Posts after a specific post ID.
- All: All available posts.
From ID The specific post ID to start fetching from. Only shown and required if "Initial Data" is set to "From ID".
Group ID The unique identifier of the group to monitor for new posts.

Output

The output is an array of JSON objects, each representing a new group post. Each object contains fields corresponding to the properties of a group post as returned by the Cativa API. Typical fields may include:

{
  "id": "string",
  "shortId": { "guid": "string" },
  "createdAt": "ISO8601 timestamp",
  // ...other post-specific fields
}
  • The output is reversed so that the oldest new post appears first.
  • In manual mode, only the most recent post is returned.

Dependencies

  • External Service: Requires access to the Cativa API.
  • API Key: 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 invalid or missing, the node will fail to connect to the Cativa API. Ensure the cativaApi credential is correctly set up.
  • No new posts detected: If the polling interval is too short or there are no new posts since the last check, the node may not trigger any workflow runs.
  • Incorrect "From ID": Providing an invalid or outdated post ID in "From ID" may result in missing some posts or duplicate triggers.

Error Messages:

  • "Authentication failed": Check your API key and permissions.
  • "Cannot read property 'id' of undefined": This may occur if the API response structure changes or is empty; verify the group ID and API status.

Links and References

Discussion