Engaging with posts

Crispy gives you a full engagement toolkit, all sharing one daily engagement budget of 100 actions so activity stays at a human level.

• react_to_post: react with one of six types: like, celebrate, support, love, insightful, or funny. Reacting again simply overwrites your previous reaction, so it is safe to repeat.
• comment_on_post: leave a comment of up to 1250 characters, either top-level or as a threaded reply by passing a parent comment ID.
• reply_to_comment: reply to a specific comment by its comment ID, up to 1250 characters. The comment must already be in Crispy's cache; run get_comment_status first to confirm. For a comment created moments ago in the same session, use comment_on_post with parent_comment_id instead.
• repost_post: reshare a post to your feed, with optional commentary. The post_id must be an activity URN like 'urn:li:activity:7123456789'.
• engage_with_latest_post: the shortcut. Point it at a person by provider ID, profile slug, or profile URL and it reacts to their most recent post, optionally leaving a comment too. It returns 'no posts found' when the person has no public posts, and you can attach the action to a campaign so the touch shows up in that contact's history.

Engagement is the classic warm-up move before outreach: react to or comment on someone's post a day or two before sending an invitation, and your name is already familiar when the request arrives.

All of these count toward the shared 100-per-day engagement cap, which resets at midnight UTC. Use get_account to see how much budget remains before queueing a batch.