Skip to main content
Every configuration requires contact_filter, trigger, opening, follow_up, and extras. Unknown fields are rejected. Use explicit null for no follow-up. The examples below are fragments; see the creation workflow for a complete request.

Select the audience

These filters restrict who can enter; they do not send a follow request or collect contact data.

Opening with a continuation button

Set this object as opening. Both public_reply and direct_message are required. An enabled public reply is only valid for a comment trigger. Disable it with {"enabled":false} for other triggers. Public replies require at least one message of 1 to 280 Unicode scalars. rotation accepts random or sequential; mention_mode accepts none, contact, or account. max_per_post is 1 to 200. Both opening delays allow 0 to 86400 seconds in the schema; non-comment direct-message openings are limited to 86399 by semantic validation. The direct message requires text and buttons. With buttons: [], text allows 1 to 1000 scalars. With 1 to 3 buttons, it allows 1 to 640. Button titles allow 1 to 20 scalars without surrounding whitespace. A start_follow_up button starts the sequence; a url button opens its HTTP(S) url. Exactly one continuation button is required when follow_up is non-null, and none is allowed when it is null.

Cooldown

Set this object as extras to configure six hours between repeated triggers. Fixed cooldown accepts 1 to 2592000 seconds. To disable it, use {"cooldown":{"mode":"none"}}. Cooldown is repeat protection, not a scheduled delivery delay.