Previous value: -"Link buttons on the delivered message, e.g. [{\"title\":\"Buy\",\"url\":\"…\"}]. THIS is where every URL goes — do not repeat it in `message`. On Instagram, Facebook, Telegram and WhatsApp they render as tappable buttons; everywhere else Ignix appends them as \"title: url\" text automatically, so the link always arrives either way."New value: +"Link buttons on the delivered message, [{\"title\":\"Get the guide\",\"url\":\"…\"}]: every URL goes here, never in `message`. Where buttons cannot render, Ignix appends them as text."

Previous value: -"Deliver a carousel instead of a message: [{title, subtitle, imageUrl, buttons:[{title,url}]}]. Mutually exclusive with mediaUrl — a carousel IS the message."New value: +"A carousel instead of a message: [{title, subtitle, imageUrl, buttons:[{title,url}]}]. Not with mediaUrl."

Previous value: -"The direct message they receive. Write the text ONLY — never paste the URL in here. The link belongs in `buttons`, and Ignix already appends it as text on the networks that cannot render buttons. Putting it in both shows it twice."New value: +"The direct message they receive: text ONLY, never the URL (it goes in `buttons`; putting it in both shows it twice)."

Previous value: -"Default true on comment triggers: someone who comments the keyword again does not get another DM (repeating the same DM to the same person is what gets accounts restricted by Meta). Set false only if the user explicitly wants repeat DMs."New value: +"Default true on comments: no second DM to the same person (repeats get accounts restricted by Meta). false only if the user asks."

Previous value: -"Required when scope is \"existing\": the posts it watches. Paste the post URL — https://www.instagram.com/reel/ABC123/ — and it is resolved against the account's real posts. A native post id works too. Do NOT try to fetch the URL yourself: Instagram blocks it, and the code in the link is not the id the webhook sends. list_posts only knows posts created from Ignix, so a Reel published from the phone will not be there."New value: +"Required for scope \"existing\": the post URLs (https://www.instagram.com/reel/ABC123/) or native ids; Ignix resolves them. Do not fetch the URL yourself (Instagram blocks it)."

Previous value: -"Alternative wordings for the public reply; one is picked per comment so the answers read naturally. They do not change platform permissions, messaging limits or who receives the message."New value: +"2-3 alternative wordings of the public reply; one is picked per comment."

Previous value: -"Demand a follow before delivering. It loops: if they still do not follow, the message is sent again. Instagram only. Also opens the 24h window."New value: +"Instagram only: ask for a follow before delivering, again until they follow. Also opens the 24h window."

Previous value: -"Required when scope is \"scheduled\": the Ignix id of the unpublished post (create_post's `post.id`, or the id list_posts shows for a draft). The automation accounts must be among that post's accounts. If the post is deleted, the automation is deleted with it."New value: +"Required for scope \"scheduled\": the Ignix id of the unpublished post (create_post `post.id` or list_posts). Its accounts must include accountIds; deleting the post deletes the automation."

Previous value: -"Which posts it watches. \"any\" = every post, present and future. \"next\" = the next post that gets PUBLISHED after this is saved (it waits for the publish event and then pins itself to that post — a draft or a scheduled post does NOT claim it, only actual publication does). \"existing\" = the specific posts in `postIds`. \"scheduled\" = ONE Ignix post that is not published yet (a draft or a scheduled post: one you create now with create_post, or one already in Ignix — saved by Ignix Creator or Editor, or found with list_posts), given in `scheduledPostId`: the automation starts answering when THAT post goes out, and no other post can claim it. For a post that is not out yet, offer \"scheduled\" FIRST: if it is already a draft in Ignix, tie the automation to that draft; if not, create it as a draft (create_post, no date) and tie it now — nothing else can take it and the person does not have to come back. Only when they will publish it outside Ignix (from the phone, for example to use a trending sound) does it need \"next\" or \"existing\" once they send the post link; say that publishing outside Ignix is what rules the draft out."New value: +"Which posts it watches: \"any\" = every post; \"next\" = the next post actually PUBLISHED (a draft or a scheduled post does not claim it); \"existing\" = the posts in `postIds`; \"scheduled\" = one unpublished Ignix post (`scheduledPostId`), answered once THAT post goes out. For a post not out yet, offer \"scheduled\" first (tie it to its draft, or create the draft now); only a post published outside Ignix needs \"next\" or \"existing\". Details: get_working_rules(\"comment-to-dm\")."

Previous value: -"What starts it. \"story\" reacts to story replies instead of comments, and it already arrives as a direct message, so the 24h window is open from the start and nothing below is restricted."New value: +"\"story\" reacts to story replies: they arrive as a DM, so the 24h window is open and nothing is restricted."

Previous value: -"Generate AI variants of every message so each person receives a differently worded copy (same meaning, same links and codes). Needs AI enabled for this workspace in its plan (the account owner can turn it on by opening the Ignix app); otherwise it is silently ignored."New value: +"AI-worded variants of every message (same meaning, links and codes) so each person gets a different copy. Needs AI on in the plan; otherwise ignored."

Previous value: -"Opening message with a button. THIS IS WHAT OPENS META'S 24h WINDOW: without it (or without requireFollow) media, carousel and asking for data are not allowed on a comment trigger."New value: +"Opening message with a button; it opens Meta's 24h window. Without it (or requireFollow), no media, carousel or asking for data on a comment trigger."

Previous value: -"Extra public replies; one is picked at random per comment, so it does not look automated."New value: +"Alternative wordings for the public reply; one is picked per comment so the answers read naturally. They do not change platform permissions, messaging limits or who receives the message."

Previous value: -"Generate AI variants of every message so each person receives a differently worded copy (same meaning, same links and codes). Needs an AI seat in the workspace (Inferno or the AI add-on); otherwise it is silently ignored."New value: +"Generate AI variants of every message so each person receives a differently worded copy (same meaning, same links and codes). Needs AI enabled for this workspace in its plan (the account owner can turn it on by opening the Ignix app); otherwise it is silently ignored."