An event node is a graph entry point. Live instances receive matching events from watched accounts, while tests supply synthetic events of the same type.
Social Post Events
Author handles are suitable for exact matching after using the corresponding break node. Store watched accounts in the reserved author variable when operators need to change the allowlist.
For the top-level fields of a tweet, connect Tweet Event > Tweet to Mini Tweet Break > Mini Tweet. Use its Author Handle, Body Text, and Type outputs for author, content, and original-post rules. Use Full Tweet Break only when the workflow needs full related-tweet content from a compatible full-tweet source.
Test exact handles and near-matches. An automation intended for elonmusk should also have a no-effect test for a similar handle.
Profile Events
Use Profile User Break when you need individual fields from a profile object.
Use More Than One Event
A graph can expose multiple root event types. Each test chooses one of those types. Route the event-specific data through its matching break node, then call shared functions for common behavior.
For example, a tweet and a Truth Social post can each expose body text and author, then call the same pure function to select an address.
Model Related Content
Tweet tests support TWEET, REPLY, QUOTE, and RETWEET. Truth Social tests support TRUTH, QUOTE, RETRUTH, and REACTION. Instagram post tests support REEL, PHOTO, and CAROUSEL; stories support IMAGE and VIDEO.
When a workflow depends on quoted or reposted content, include that related content in the test and use the full-event path in the graph.
Graph tests use normalized event fixtures rather than pasted social-network API responses. For an original tweet, choose TWEET and provide the author handle and display name, body text, and an image list. Use an empty image list when the post has no media. Add related content only when modeling a reply, quote, or retweet.
When a request says an account “posts” but does not mention replies, quotes, or retweets, use TWEET for the positive case. Add the other tweet types as no-effect cases when excluding them is part of the required behavior.