Has Done - Captain
AI-generatedOverview
This node checks if users have performed a specified event within a defined time range. It is useful in workflows where you need to verify user actions based on event data, such as marketing automation, user engagement tracking, or conditional branching based on user behavior. For example, it can check if users have completed a purchase event since the last segment retrieval or within a custom time frame.
Use Case Examples
- Check if users have done a 'purchase' event since the last segment was retrieved to trigger a follow-up campaign.
- Verify if users have performed a 'login' event within the last 24 hours to personalize content delivery.
Properties
| Name | Meaning |
|---|---|
| This node checks if the user has done an event since last get segment node (based on event) or event trigger node | Informational notice describing the node's purpose. |
| List of Events To Check If Has Done Name or ID | Select the event to check if the user has done. |
| Time Range | Defines how far back the event should be checked, with options for 'Since Last Get Segment', 'Forever', or 'Since Time'. |
| Amount | Numeric value for the time range when 'Since Time' is selected, specifying how far back to check. |
| Time Unit | Unit of time for the 'Amount' property, such as minutes, hours, days, or months. |
| Wait Until DND | Boolean flag to wait until all messages are sent before proceeding. |
| Users | Comma-separated list of user IDs to check. Leave blank to use users from the previous node. |
Output
JSON
jsonuserId- The ID of the user checked.outputResult
*hasDone- Boolean indicating if the user has done the specified event.
Dependencies
- Requires an API key credential for authorization to access the external event tracking API (environment variable UNEXO_API_KEY).
- Requires the base URL of the external API set in environment variable CDP_URL.
Troubleshooting
- Error if the node is used without a preceding 'Get Segment' or 'Event Trigger' node when 'Since Last Get Segment' time range is selected. The error message indicates the missing prerequisite node.
- HTTP request failures to the external API are retried up to 3 times with delays; persistent failures will log errors and may cause the node to fail.
- Ensure environment variables CDP_URL and UNEXO_API_KEY are correctly set and valid to avoid authorization or connection errors.