Overview

This node checks if the content has been sent by examining the input data for a specific property indicating a sent status. It separates the input items into two outputs: those that have been sent and those that have not. This is useful in workflows where you need to branch logic based on whether content has already been processed or sent, such as in messaging or content distribution systems.

Use Case Examples

1. In a messaging workflow, use this node to filter messages that have already been sent to avoid duplicates.
2. In a content publishing pipeline, use this node to separate content that has been published from content that is still pending.

Output

JSON

• true - Items where content has been sent (contentId exists and is not null)
• false - Items where content has not been sent (contentId is missing or null)

Troubleshooting

• Ensure that the input data contains the 'outputResult' object with a valid 'contentId' property; otherwise, items may be incorrectly classified as not sent.
• If all items appear in the 'false' output, verify that the input data structure matches the expected format with 'outputResult.contentId'.