# Ignix — full help centre Every article of the Ignix help centre in one file, in the order of the sidebar. Generated from the site itself, so it never disagrees with the pages. Index: https://ignix.social/llms.txt ============================================================================== SOURCE: https://ignix.social/help/what-is-ignix ============================================================================== # What Ignix is Ignix is an all-in-one social media platform. It replaces three separate tools: a post scheduler, a DM/comment automation tool, and a shared inbox with an AI support agent. ## Ignix can - Schedule and publish posts to Instagram, TikTok, Facebook, LinkedIn, X (Twitter), YouTube, Threads, Pinterest, Reddit, Bluesky, Telegram, Snapchat and Google Business Profile. - Turn comments into private DMs automatically (Instagram and Facebook). - Reply automatically to story reactions and replies (Instagram). - Run chatbot flows with buttons, delays, conditions and AI answers. - Answer customers with an AI agent that learns the business, across DMs, comments and a web chat widget, and hand the conversation to a human. - Show analytics for posts, accounts and inbox performance, and export them as a client-ready PDF report. - Watch X and Reddit for mentions of your brand, label everything you receive as positive, neutral or negative, and warn you when negativity spikes (needs AI). - Write captions, generate images and generate video with AI. - Take appointments: booked with buttons in the web chat and in DMs, on a public booking page or by talking to Sparky, straight into Google Calendar, with branded confirmation and reminder emails. Contacts and messages are unlimited from the Blaze plan; Spark includes 1,000 automated replies a month. You are only charged per connected social account. The sidebar menu contains: My Accounts, Posts, Analytics, Inbox, Appointments, Reddit Radar, Google Business Profile, Automations, Sparky AI, Contacts, Organization, Billing, Settings. Some entries only appear when they are relevant (for example Google Business Profile appears once a Google Business account is connected). ============================================================================== SOURCE: https://ignix.social/help/getting-started ============================================================================== # Getting started in 10 minutes ## Step by step for a brand-new account A short guided tour runs the first time you enter the app and points out the main sections. You can skip it, and you can start it again whenever you want from Settings > Welcome tour. It is per user: replaying it does not reopen it for the rest of your team. 1. Create your account and confirm your email. 2. Go to My Accounts (the first menu entry). 3. Click "Connect a new account" and connect your first social network. 4. Go to Posts and click "New post" to write and schedule your first post. 5. Go to Sparky AI > Knowledge and fill in your business name, description and website so the AI assistant can answer your customers correctly. 6. Go to Automations if you want comments to trigger automatic DMs. You do not need to configure anything else to publish. Everything else is optional. ============================================================================== SOURCE: https://ignix.social/help/connecting-accounts ============================================================================== # Connecting social accounts > **Where:** My Accounts (first menu entry). ## To connect an account 1. Go to My Accounts. 2. Click "Connect a new account". 3. Choose the social network. 4. Log in on the network's own page and grant the permissions it asks for. 5. You are returned to Ignix and the account appears in your list. You can connect several accounts of the same network. Each connected account counts against your plan's account allowance. If a connection fails or connects the wrong profile: log out of that social network in your browser first, then connect again. The network reuses whichever session is already open in your browser. Instagram requires a Business or Creator account. Personal Instagram accounts cannot post through any API, including Ignix. Facebook connects PAGES, not your personal profile. You log in with your own Facebook account, but what gets connected is the Page (or Pages) you administer. If your account manages several Pages, they all connect, and in the composer you pick which one each post goes to. LinkedIn works the same way with company pages: choose which one to publish as. ## Telegram is connected differently, with a code 1. Go to My Accounts and choose Telegram. 2. Click to generate an access code. 3. Open the bot link shown on screen. 4. Send the bot the access code. 5. Return to Ignix and click "Check connection". Bluesky is connected with your handle and an app password (not your normal password). Create the app password in your Bluesky settings, then enter your handle and that app password in Ignix. To disconnect an account, open My Accounts and remove it from the account's menu. Removing an account frees its slot in your plan. ============================================================================== SOURCE: https://ignix.social/help/scheduling-a-post ============================================================================== # Writing and scheduling a post > **Where:** Posts > "New post". ## Step by step 1. Go to Posts. 2. Click "New post". 3. Under ACCOUNTS, click the accounts you want to publish to. You can select several networks at once. 4. Write your text in the main box. 5. Drag your images or videos into the MEDIA area, or click to upload. Grab the numbered handle on a thumbnail to change the order — the first one is the cover. 6. Check the per-network preview underneath. Each network shows its own character count and the format it will publish as. 7. Choose when to publish: publish now, or pick a date and time. 8. Click Schedule (or Publish now). To save without publishing, use the draft option. Drafts are listed under the calendar and can be reopened, duplicated or deleted. Per-network text: in the preview area, click "Customize" next to a network to write different text just for that network. Click "Use global" to go back to the shared text. Time zone: posts are scheduled in your organization's time zone, which you set in Settings. ============================================================================== SOURCE: https://ignix.social/help/post-formats ============================================================================== # What format each post publishes as In the composer, each network row shows a badge with the format that will actually be published: Text, Photo, Carousel, Gallery, Video, Reel, Story, Thread or Document. Instagram decides the format from the media, not from a dropdown: - 1 photo = a normal feed post. - 2 to 10 files = a carousel. Photos and videos CAN be mixed in the same Instagram carousel. - 1 single video and nothing else = a Reel. - To publish a Story instead, choose "Story" in the Instagram post type option. Facebook has a post type option with Feed, Reel and Story. The composer also warns you when your images do not fit a network. Instagram feed and carousel images must have an aspect ratio between 0.8 (4:5 portrait) and 1.91 (landscape). A 9:16 vertical image has to be published as a Story, or cropped. Use the crop button on the image to fix it to 4:5, 1:1, 1.91:1 or 9:16. In an Instagram carousel all items should share the same aspect ratio, because Instagram applies the ratio of the FIRST item to the whole carousel and crops the rest. Ignix warns you when the ratios do not match. ============================================================================== SOURCE: https://ignix.social/help/network-limits ============================================================================== # Network limits you should know ## Character limits for the post text - X (Twitter): 280 - Bluesky: 300 - Threads: 500 - Pinterest: 500 (plus a 100-character title) - Google Business Profile: 1,500 - Snapchat: 160 (Stories take no caption at all) - Instagram: 2,200 - TikTok: 2,200 - Discord: 2,000 - LinkedIn: 3,000 - Telegram: 4,096 (1,024 when the message carries media) - WhatsApp: 4,096 (1,024 when the message carries media) - YouTube: 5,000 description, plus a 100-character title - Reddit: 40,000 body, plus a 300-character title (title required) - Facebook: 63,206 ## Media limits - Instagram: up to 10 items per post, photos and videos can be mixed. - X (Twitter): up to 4 images OR 1 video. Images and video cannot be mixed. - Facebook: up to 10 images, no mixing images and video. - LinkedIn: up to 20 images, single video. - TikTok: 1 video, or a photo carousel of up to 35 images. Cannot mix. - Pinterest, Snapchat, Google Business Profile: a single media item. - Threads: up to 10 images. - Telegram: up to 10 images and 10 videos. Instagram allows a maximum of 5 hashtags per post. Ignix blocks publishing with more and offers to fix it for you. WhatsApp is a messaging channel only. It cannot be used as a destination for scheduled posts. ============================================================================== SOURCE: https://ignix.social/help/network-options ============================================================================== # Network-specific options In the composer, under each network in the preview area, there is a "Network options" section with settings that only apply to that network. Examples: - Instagram: post type (Feed/Carousel/Reel or Story), share Reel to feed, first comment, collaborators, tag users, Trial Reel, cover image or cover second, AI-generated media label. - Facebook: which Page to publish to, post type (Feed, Reel, Story), Reel title, cover image, first comment, save as draft on the Page, country restriction, multi-link carousel and its "See more" link. - TikTok: post type, privacy, allow comments/Duet/Stitch, the two mandatory confirmations, commercial content disclosure, AI disclosure, cover image or cover second, carousel description and cover photo, auto background music. - YouTube: title, tags, custom thumbnail, visibility, first comment, made for kids, AI disclosure, category, playlist. - Pinterest: title, board, destination link, cover image or cover second. - Reddit: subreddit, title, link post, flair, Reddit video player, cover image, looping clip, NSFW, spoiler, reply notifications. - LinkedIn: which company page to publish as, country restriction, first comment, document title, disable link preview, repost with your commentary. - X (Twitter): poll, reply settings, thread editor, quote a post, long video, country restriction, paid partnership, AI-generated media, sensitive media. - Threads: topic tag, thread editor. - Bluesky: thread editor. - Telegram: text formatting, silent send, protected content, no link preview. - Google Business Profile: which listing, post type (update, event or offer), event dates, offer coupon and terms, language, call-to-action button. Two of these deserve their own explanation, because they are the ones people ask about. VIDEO COVERS (THUMBNAILS) ------------------------------------------------------------ The image someone sees before they press play. You can set one on: - YouTube — regular (horizontal) videos. NOT on Shorts: YouTube's API does not accept a custom thumbnail for a Short, so the field is hidden when your video is vertical rather than offered and silently ignored. Your channel must be phone-verified for YouTube to accept custom thumbnails at all. - Facebook — video posts and Reels. - Instagram — Reels. - TikTok — videos and carousels. - Pinterest — video pins. ## Two ways to set it, wherever it is offered - Cover image: upload a file (JPG or PNG). Always a file — you never paste a URL. - Cover second: type the second of the video to freeze, e.g. 2.5. If you upload an image as well, the image wins. The cover field lives on the video itself, under the media, not in the network options — that is where to look for it. MULTI-LINK CAROUSEL (FACEBOOK) ------------------------------------------------------------ Turns your images into a swipeable carousel where each image is clickable and opens its own web page. Useful for a product roundup: five products, five images, five links. - Add one card per image. Three images means three cards; Facebook rejects the post if the numbers do not match, and Ignix warns you before you publish. - Between 2 and 5 images. Images only — no videos. - Each card takes the link it should open, and optionally a title and a short description shown under the image. - "See more link" is an EXTRA card Facebook adds at the end, after your images, with a "See more" button. It is optional; left empty it reuses the first image's link. TIKTOK PHOTO CAROUSEL: TITLE OR CAPTION ------------------------------------------------------------ The same text box means two different things on TikTok, depending on the post type, and this is the one that catches people out. | Post type | The main text is… | Limit | Carousel description | |---|---|---|---| | Video | The caption | 2,200 | not used | | Photo carousel | **The title** | **90** | The real caption, up to 4,000 | On a photo carousel, TikTok cuts the title at 90 characters **and strips out hashtags and URLs**, without telling you. So a 600-character caption with five hashtags typed into the main box arrives as a cropped title with no hashtags at all. Write a short hook in the main box, and put everything else — caption and hashtags — in "Carousel description". The character counter in the composer follows the post type, so it shows 90 as soon as you choose Photo carousel. ============================================================================== SOURCE: https://ignix.social/help/calendar-and-drafts ============================================================================== # Calendar, drafts and failed posts > **Where:** Posts. The calendar shows every scheduled and published post. Each post shows a status: Draft, Scheduled, Publishing, Published or Failed. Filters above the calendar narrow it by network and by account, which is what you want when one workspace holds several accounts of the same network. There is also a full-screen view for planning. - To reschedule: drag the post to another day. - To edit: click the post and open it in the composer. - To retry a failed post: open it and use Retry. - To remove a published post from the network: use Unpublish. This is supported on Threads, Facebook, X, LinkedIn, YouTube, Pinterest, Reddit, Bluesky, Google Business Profile and Telegram. On other networks it only removes it from your calendar and you must delete it in the network's own app. Queue: you can define recurring time slots (for example Tuesdays at 10:00) and have posts fill the next free slot automatically instead of picking dates by hand. Set the slots in the queue settings on the Posts page. Bulk import: you can import many posts at once from a CSV or JSON file, up to 100 items per import. ============================================================================== SOURCE: https://ignix.social/help/content-library ============================================================================== # Content library > **Where:** Posts page, the Library section. ## The library stores reusable material - Media: images and videos you have used or generated. Insert them into a new post with one click. - Hashtag groups: save sets of hashtags with a name and paste them in later. - Snippets: save text fragments you repeat often (a CTA, a disclaimer, a signature). Media generated by AI and media from your published posts is saved here automatically. ============================================================================== SOURCE: https://ignix.social/help/ai-in-the-composer ============================================================================== # AI in the composer > **Where:** Posts > "New post", the row of AI buttons under the text box. - Generate: writes a caption for you. Type your idea first, or leave it empty and pick "Post idea" to have the AI propose one. - Adapt to network: rewrites your existing text in the style and length of a specific network. - Translate: translates your text. - Hashtags: suggests up to 5 relevant hashtags. - Image: generates an image from a text prompt, or edits an image already in the post. - Video: generates video, if you have configured a video provider key. The AI always answers in the language you wrote in. If you write your brief in English, the caption comes out in English. Autopilot goes further: it plans a whole campaign — up to 16 pieces spread over a week or a month, each with a different angle, written in every account's own voice and carrying a suggested date. Everything lands as drafts for you to review; it never publishes directly, and by default no network is ticked. It has its own article in this section. Whatever the AI writes or designs follows your own posting style, which Ignix learns from the posts your accounts have already published. See the next section. Image generation is included from the Blaze plan: 30 a month (80 on Scale, 300 on Inferno). Video generation uses your own provider key, with a starting image (image-to-video), pro/1080p quality, duration and more options depending on the provider. Every prompt for image or video generation is checked against our content policy before it is generated. If a prompt is rejected, rewrite it and try again. ============================================================================== SOURCE: https://ignix.social/help/autopilot ============================================================================== # Autopilot: plan a week of content > **Where:** Posts > the "Autopilot" panel above the calendar. Autopilot plans and writes content for you, and everything it makes lands as drafts — it never publishes on its own. Pick the accounts, how many pieces (1 to 16) and the period: today, this week or this month. Add a brief if you have one; leave it empty and Autopilot picks high-value topics for your brand. Then: - One strategist pass plans the campaign: a different angle per piece — educational, proof, story, contrarian — spread across the period, informed by what you already published so it does not repeat you. - Every piece is then written for each account you selected, in that account's own learned voice, and natively for its network: caption length, hooks, CTAs and hashtag habits differ between Instagram, X, LinkedIn or Reddit on purpose. - Facts from your brief — prices, names, dates — are locked and survive every adaptation unchanged. If your brief or brand context is too thin to plan well, Autopilot says what is missing in an amber note instead of inventing. ## Suggested dates Each draft carries a suggested date, taken from your posting queue for that weekday when you have one, or from your accounts' best posting times, in your organization's timezone. The date is a proposal: open the draft and press schedule to confirm it, or change it first. The drafts list shows each proposal as a small calendar chip. ## Formats, images and video By default the strategist chooses the format per piece among what your selected networks support (post, carousel, story, reel). With several networks selected you can force a format per network — a carousel on Instagram and a plain post on X, say. Images count against your plan's monthly quota; when the quota runs out, Autopilot keeps going with text only. Reels use your own video provider key and, if you asked for images, the video animates a brand image generated in your account's style rather than starting from a blank prompt. ## Cost and plans Autopilot is included from the Blaze plan. If your team uses content approval, Autopilot drafts go through the same review as everything else. ============================================================================== SOURCE: https://ignix.social/help/posting-style ============================================================================== # Posting style learned from your accounts > **Where:** Sparky AI > Train, the "Posting style, learned from your accounts" panel. Ignix looks at what your connected accounts have already published and works out three things, so that anything it creates for you looks and sounds like you instead of like a stock brand: - Your colours, each with its role: which one is the accent that identifies the brand, which is the background, which is the text colour, and the ends of any gradient or glow. - How your posts are built: layout, typography, treatment, the elements that repeat across your posts (logo placement, frames, grids), and what would look wrong for your brand. - How you write, per network. A brand does not write the same way on X as on LinkedIn, so a network with at least four published posts gets its own description; the rest fall back to a general one. This shapes NEW POSTS ONLY — the composer and Autopilot. It does not change how Sparky replies in chat, DMs or comments; that is set in the Knowledge sections of the same page. ## What it learns from - Only posts that actually reached a network, including the ones published natively outside Ignix. Images you generated with AI but never published are ignored on purpose, so the AI never learns from its own output. - Images only. From a video post it uses the thumbnail, which is a real frame of yours. ## When it runs - Automatically once a week. A brand's style does not change from one day to the next. - Or immediately, with the "Learn now" button, which is what to use right after connecting your accounts for the first time. If the panel shows nothing, you have no published posts with images yet. If it shows your colours and how you write but no "How your posts are built" block, an amber note explains exactly why the images could not be read. The captured voice is a starting point, not a verdict: you can edit the text of any voice block by hand, and once you do, the weekly sweep never overwrites it ("Back to what was learned" undoes your edit). Colours and composition are measured, not written: if a colour looks wrong, press "Learn now" again after publishing posts that better represent the brand. ## Style per account Below the workspace panel sits "Posting style, per account": one collapsed card per connected account. Each account learns its OWN palette, its own composition guide and its own voice, from what that account publishes — three visually different Instagrams keep three different styles, and content generated for an account uses what THAT account learned. The workspace style is the fallback while an account has not learned yet. An account's voice is learned from all of its posts, with or without images — an X account that only posts text still learns how it writes. The palette and the composition guide need posts with images. ## Style examples you add > **Where:** inside each style card, the "Style examples you add" block. Have posts on accounts that are NOT connected to Ignix — an old TikTok, another brand of yours, a client's account you run elsewhere? Paste their captions or upload their images there and the learner mixes them with what your connected account publishes. It is how a brand-new account can already sound like one you have been cultivating for years. Nothing you add here is ever published: it is only used to learn. You choose where it goes. Open the block inside the general card and it feeds the workspace style; open it inside an account's card and it feeds only that account. ## What to add, and how much - TEXTS: one post per block, separated by a blank line (or a line with ---). Around 10 useful captions is the minimum, 20 is plenty and past 50 it stops improving. Variety matters more than volume: ten different posts teach more than ten identical promos. Anything under 15 characters is dropped, and so are duplicates. - IMAGES: 6 to 12 pictures from real posts. Pictures, NOT screenshots of the post — a screenshot brings in the app's interface (its whites, its blues, its font) and poisons the measured palette. - The minimums are a warning, never a wall: with less material it still learns, and the counter tells you where you stand. VIDEO ACCOUNTS. This is the answer to a real gap. From YouTube and TikTok we read titles and descriptions, never the video itself — no transcripts and no frames — so what is learned is a headline voice, not the way you actually talk. Paste the transcripts or scripts of your videos and that gap closes: a transcript is the richest voice sample there is. YouTube generates automatic subtitles you can copy in two clicks, and thumbnails uploaded as images give the palette. ## Removing it Each example has its own bin, and there is a "Delete all" for the whole destination. The automatic re-learning never deletes what you added — it is material you put there on purpose — but removing it is always one click away. After deleting, press "Learn now" in the same block so the style goes back to what your connected account shows, instead of waiting for the weekly sweep. ============================================================================== SOURCE: https://ignix.social/help/inbox ============================================================================== # Inbox — DMs, comments and reviews > **Where:** Inbox. ## The Inbox brings together, in one place - Direct messages from Instagram, Facebook, Telegram and WhatsApp. - Comments on your posts from Instagram, Facebook, X, YouTube, LinkedIn, Bluesky and Reddit. - Google Business Profile reviews. ## What you can do - Reply to a message or a comment. - Send a private DM in reply to a public comment (Instagram and Facebook). - Attach an image, a video, a file or a voice note, depending on the network. - Send buttons or quick replies (Instagram, Facebook, Telegram). - Hide, delete or like a comment, where the network allows it. - Mark a conversation as read, assign it a stage, and filter by network, account or status. - Use Saved replies to answer common questions with one click. When you reply to a conversation that an AI agent is handling, the AI stops answering that conversation automatically so you do not talk over each other. Mark the conversation as handled to give it back to the AI. Instagram and Facebook only allow you to send a message within 24 hours of the customer's last message. Outside that window the network blocks the send. REVIEWS THAT ANSWER THEMSELVES ------------------------------------------------------------ When a new review lands on a connected Google Business listing, Ignix can do two things without you. - **Alert the team** at three stars or below, by email, with the text of the review and a link to reply. - **Reply on its own** at four stars and up — either with AI in your brand voice, or with your own texts. If you write your own, put in a few: Ignix rotates between them, because the same sentence under fifty reviews is what gives a bot away. That split is deliberate. A one-star review needs an answer, but not a generated one: an automatic text in front of an angry customer reads as a form letter and makes things worse. Those come to you instead. Auto-reply is off until you turn it on, and it never replies twice — if someone on your team got there first, it leaves it alone. Both settings live in Settings, next to the reputation alert, and both notify the same team. ============================================================================== SOURCE: https://ignix.social/help/live-visitors-and-tickets ============================================================================== # Live visitors and tickets Live visitors (Sparky AI area): shows who is browsing your website right now, which page they are on and how long they have been there. You can start a chat with a visitor before they write to you. Tickets: when a conversation needs follow-up, a support ticket is created with a number, a subject, a priority and notes. You can filter tickets by status, priority and assignee, and search them. The AI assistant can open a ticket by itself when the case needs it. ============================================================================== SOURCE: https://ignix.social/help/comment-to-dm ============================================================================== # Turning comments into DMs > **Where:** Automations > "Comment→DM Flow". This is the simplest automation and the most used one. When someone comments a keyword on your Instagram or Facebook post, Ignix sends them a private DM. ## Step by step 1. Go to Automations and open the "Comment→DM Flow" tab. 2. Choose the account and, if you want, the specific post it applies to. 3. Write the keyword or keywords that trigger it. 4. Write the DM that will be sent. 5. Optionally add: a public reply to the comment, a welcome message with a button, a follow requirement, an email capture step, or a handoff to a human. 6. Save and activate. **Vary the messages with AI** (with an AI seat: the Inferno plan or the AI add-on): each person gets a different version of every message — same meaning, same links and codes — so the automation doesn't read like one. More in "Chatbot flows in the visual builder". Private replies to comments only work on Instagram and Facebook. Other networks allow comment replies but not private DMs. ## Limits set by Meta (not by Ignix) - **One private reply per comment.** After a comment, Meta lets the automation send exactly one message: text and up to 3 buttons, with no image or video. Everything else in the flow — a second message, media, a question — is sent once the person replies, either by writing or by tapping a reply button (link buttons don't count). The editor marks those steps with "Sent once the person replies to the first message". - **Facebook only answers personal profiles.** Comments made as a Page — including your own Page — never receive a private reply, so nothing happens for them. - **7 days.** The private reply must go out within 7 days of the comment. - **Testing it:** comment from another account. On Facebook, use a personal profile (not a Page); on Instagram, an account other than the connected one. ============================================================================== SOURCE: https://ignix.social/help/story-replies ============================================================================== # Story reactions and replies > **Where:** Automations > "Story reactions". When someone reacts to or replies to your Instagram story, the network delivers it as a DM. Ignix can answer automatically. ## Step by step 1. Go to Automations and open the "Story reactions" tab. 2. Choose the account. 3. Choose whether it applies to any story or to one specific active story. 4. Optionally restrict it to certain keywords in the reply. 5. Write the automatic reply. 6. Save and activate. **Vary the messages with AI** (with an AI seat: the Inferno plan or the AI add-on): each person gets a different version of every message — same meaning, same links and codes — so the automation doesn't read like one. More in "Chatbot flows in the visual builder". ============================================================================== SOURCE: https://ignix.social/help/chatbot-flows ============================================================================== # Chatbot flows in the visual builder > **Where:** Automations > "My automations", then open or create a flow. The flow builder lets you design a full conversation. Available blocks include: - Send a message, with or without media. - Ask a question and wait for the answer — with a timeout branch, so someone who never replies gets a reminder instead of being forgotten. - Buttons and quick replies, each opening its own branch. - A card carousel (Instagram and Facebook). - Delay (wait minutes, hours or days before the next step). - Conditions, for example whether the person follows you. - Tag the contact, save their data, or capture an email. - Book an appointment with buttons (service → day → time → details), without AI. See "Appointments". - Ask the AI to answer freely using your knowledge base. - Hand the conversation to a human. - A/B split, to alternate between two branches and compare results. ## Step by step 1. Go to Automations > "My automations". 2. Create a flow and choose the trigger (a comment, a DM, a keyword, a story reply). 3. Drag blocks onto the canvas and connect them. 4. Save and activate the flow. Quick templates: the "Templates" tab has ready-made automations you can set up by filling in a short form, without touching the builder. ## Vary with AI When the same message goes out to a lot of people, it starts to look like what it is: an automated message. Under the text of every block that sends something (message, buttons, question, media, public reply…) there is a check, **Vary with AI**. When you save, Ignix writes fifteen versions of that message — same meaning, same tone, same language, with links, codes and numbers kept exactly as they are, and never longer — and each person gets a different one, picked at random alongside yours. There is nothing to review: the versions aren't shown, and if you edit the text they are discarded and written again. It needs an AI seat in the workspace (the Inferno plan or the AI add-on). If you drop it later, the versions already written keep working; new ones just stop being generated. ## Media in a DM What travels, and how, depends on the network. On Instagram and Facebook a message with buttons is a template, and a template only carries an image. So each kind of file takes the route that looks best in the chat: | What you attach | How it arrives on Instagram and Facebook | |---|---| | Image | Inside the message, above the buttons | | Video | As its own message right before the buttons — it plays in the chat | | Audio | As its own voice message | | Document | As a **link button** you name, pointing at your file | Documents can be **PDF, Word, Excel, CSV or ZIP**, up to 200 MB, and they live on our own domain — you do not have to paste a Drive or Dropbox link into a DM and hope people trust it. Name the button ("Download the guide") and we fill in the link. Its taps are counted like any other button in the flow. On WhatsApp and Telegram the media travels alongside the buttons, so nothing changes there. Two limits that Instagram enforces quietly, without an error: - Audio must be AAC, M4A, WAV or MP4. MP3, OGG and WebM are dropped — a recording made in Chrome or on Android is WebM, while Safari records MP4. - A video attached to a DM cannot exceed 25 MB. The builder warns you about both before you send. ============================================================================== SOURCE: https://ignix.social/help/appointments ============================================================================== # Appointments: bookings from the chat > **Where:** Appointments (in the side menu). Your customers book appointments from the web chat, by DM on Instagram, Facebook, WhatsApp or Telegram, or by talking to Sparky. Every appointment lands in a Google calendar that Ignix creates for each person or room in your business, with an automatic reminder. Appointments you take by phone go in that same calendar and Ignix respects them: it never offers a time that is taken. ## Setting it up 1. Go to Appointments. 2. **Services**: what can be booked, how long each one takes, the price if you want it mentioned, and a buffer before or after if you need one (cleaning up, travelling). 3. **People and rooms**: who or what gets booked. Each one has its weekly hours, its days off and its spots at the same time (1 for a person; 10 for a class with 10 places). 4. **What to ask when booking**: name, phone, email, and your own questions ("Is it your first visit?"). Everything lands in the contact's profile. 5. **Rules**: how often slots are offered, the minimum notice, how far ahead people can book, whether they can choose who with, when the reminder goes out, and the currency prices are shown in (type just the number in each service). 6. **Connect Google Calendar** with the business's Google account. Ignix creates one calendar per person or room; share each one with that person from Google and they will see their appointments on their phone (step by step in "Several people on the team", below). 7. Turn appointments on with the switch at the top. ## How a customer books - **On your website**: the chat shows a "Book" button that opens a picker: service, day, time, details, confirm. No AI involved. - **By DM**: the flow builder has an "Appointment" block that does the same with buttons: quick replies on Instagram, Facebook and Telegram, a list on WhatsApp. Hang it off any keyword you like ("BOOK") or off a comment. The "Book an appointment by DM" template in the gallery comes ready: keyword → appointment → thanks, and a person if there is no slot. - **With a link**: the public booking page (Appointments > Booking page) works for your Instagram bio, a QR code or your website, and from there you can set it as the "Reserve" button on your Google Business listing. - **Talking to Sparky**: with the AI agent, Sparky books in conversation ("I'd like a haircut on Thursday afternoon"), answers questions along the way, and cancels or moves the appointment if asked. ## Where to put the link The public page (Appointments > Booking page) is a plain link: `app.ignix.social/book/your-business`. Where to put it so people book: - **Google (Maps and Search)**: if your Google Business listing is connected in Ignix, press "Set as the Reserve button" on the page card and the listing shows a **Book online** button with your link. Without the listing connected, do it by hand: business.google.com > Edit profile > Bookings > Add link. - **Instagram**: Edit profile > Links > Add external link, with a title like "Book an appointment". Also as a link sticker in a highlighted story. Instagram's "Book now" profile button is reserved for Meta's own partner apps and does not take a link of your own — which is why on Instagram what really books is the DM, with the "Appointment" block or with Sparky. - **Facebook**: on your page, the **"Book now"** action button does accept any link: Edit action button > Book now > your link. - **WhatsApp Business**: in the business profile, in the "Website" field; and in the welcome message. - **TikTok and the rest**: the bio link. And a QR code at the counter, pointing to the same page. ## Your page as a storefront In Appointments > Booking page you can add, all optional, a cover photo, two lines of introduction, the address (with a Google Maps link), your opening hours (worked out from the hours of the people who take bookings) and a photo per service. And you can **show your web chat on the page**: visitors ask in the chat and Sparky answers if you have it on. That way a business without a website has its page, with bookings and support, on Ignix. ## Google Calendar is the source of truth Everything Ignix books shows up in that person's calendar. And everything you write there yourself — a phone booking, a holiday, a meeting — blocks the slot. That is why manual appointments must go **in the calendar Ignix created** ("Ignix · Ana"), not in another one. If you move or delete an appointment in Google, Ignix sees it within minutes and tells the person who booked: an email with the new time, or a notice that it has been cancelled. If you drag the appointment onto another person's calendar, it is reassigned on its own. A new time is not taken for granted: the email asks the customer to **confirm it with a button** and warns that without confirmation the appointment may be cancelled. Until they do, the event shows **in red** in Google Calendar and as "new time not confirmed" in Appointments; when they confirm, it turns green. If the reminder goes out and they still have not confirmed, your team gets an alert with their phone number: better a call than a customer turning up at the old time. ## Several people on the team: one calendar each Ignix does not connect to each worker's Google account. It connects to **one** account, the business's, and creates inside it a separate calendar for every person you add in People and rooms: "Ignix · Ana", "Ignix · Luis". People and rooms and Organization > Team are two different lists: a worker needs no Ignix login to take bookings, and inviting someone to the team does not make them bookable. To give everyone their agenda: 1. **Connect the business's Google account**, not a worker's. The calendars live in it, and so does the address customers reply to. When someone leaves, nothing has to move. 2. **Add each person** in People and rooms with their own hours and days off; Ignix creates their calendar on the spot. In each service, "Who does it" says who performs it, and in Rules you decide whether the customer picks who with or gets the first person free. 3. **Share each calendar with its worker.** On the person's card, "Share it in Google" opens that calendar's settings (be signed in to Google with the account you connected). Under sharing with specific people, add the worker's Google address with permission to **make changes to events**. They accept the invitation and the calendar appears in their Google Calendar, on the phone too; if it doesn't, in the app's settings pick the calendar and turn on sync. 4. **Each worker writes in their own calendar.** A phone booking, a day off, a personal appointment: everything goes into "Ignix · Ana", choosing that calendar when creating the event. Ignix only reads the calendars it created, so what they keep in their personal calendar blocks nothing. If a worker uses Apple Calendar or Outlook, the same settings page has a secret address in iCal format they can subscribe to: read-only, so their phone bookings still go in through Google. When someone leaves, remove them from the calendar's sharing and untick "Available for booking" on their card; the calendar stays in Google with its history. What the team sees inside Ignix is a separate matter: owners and admins get the alert for every new booking, the Appointments page lists what was booked through Ignix, and whoever uses the MCP connector can check slots or book from their assistant. ## Emails and alerts Whoever books receives, if they gave an email, the **confirmation** with the appointment attached to add it to their calendar, the **reminder** at the hours you choose (24 h, 2 h…), and an email if the appointment **changes time or is cancelled**, whether you cancel it from Ignix or in Google. They carry your business's name, colour and logo (the web chat's), and where a customer's reply lands is your choice, in Rules: nowhere, the Google Calendar account you connected, or another address. In the web chat everything is also left in the conversation. By DM, Instagram, Facebook and WhatsApp only allow messages within 24 hours of the customer's last message, so there the email is the safe one. Telegram has no such window: whoever books there also gets the change, the cancellation and the reminder in the same chat. Your team (owners and admins) gets an alert with the customer's details on every new booking, and another if the customer cancels by talking to Sparky. Each person receives it by email or notification according to their preferences, in Sparky AI > Settings. What the customer tells you when booking lands on their **contact card**: the email in its own field, and the phone and your custom questions as custom fields (named after the question). They also get the `booking` tag, so you can filter Contacts down to everyone who has ever booked. If they book from the public page or you book them from your AI assistant and no contact exists yet, one is created. ## From your AI assistant If you use the MCP connector, your assistant gets five appointment tools: see how they are set up, check free slots, book (an appointment that comes in by phone while you talk to it), list the upcoming ones and cancel. Same agenda, same Google Calendar. ## Plans Bookings with buttons (web and DM) are included from Blaze. Sparky booking in conversation is part of the AI agent: included in Inferno, or with the AI pack on any plan. ============================================================================== SOURCE: https://ignix.social/help/nodes ============================================================================== # Automation nodes and triggers Every block you can drop on the automation canvas, what it does, the fields it takes and where it can continue to. This page is generated from the same table the visual builder and the MCP server read, so it cannot drift from the product. ## How a flow runs A flow starts at a **trigger** and walks from node to node along its outputs. A node that waits for a reply pauses the flow until the contact answers; a terminal node ends it. If a node needs something the network does not support, it is skipped at runtime rather than breaking the flow. ## Triggers What starts a flow. | Trigger | What starts it | | --- | --- | | `keyword` | Fires when an incoming direct message matches one of the keywords. | | `comment` | Fires on a comment on your posts. Instagram and Facebook only — they are the ones that allow answering a comment by direct message. | | `story` | Fires when someone replies or reacts to a story, which arrives as a direct message. | | `welcome` | Fires once, on the contact's first ever conversation. | | `manual` | Never fires on its own. For flows you start by hand or reach from another one. | ## Nodes ### start Entry point of the flow. Every graph has exactly one. Outputs: `next` (Node to continue to.) ### message Send a plain text message. | Field | What it does | | --- | --- | | `text` · `text` · **required** | Message body. | Outputs: `next` (Node to continue to.) ### image Send an attachment (image, video, audio or file) with an optional caption. > Needs the `dmAttachments` capability on the target network. | Field | What it does | | --- | --- | | `url` · `string` · **required** | Public https URL of the file. | | `caption` · `text` | Text sent alongside the attachment. | | `mediaType` · `select` · one of: `image`, `video`, `audio`, `file` · default `image` | Kind of attachment. | | `mediaButtonTitle` · `string` | Label of the link button used to deliver a document (mediaType "file") on Instagram and Facebook, where an attached document opens behind a Meta interstitial. Defaults to the file extension. | Outputs: `next` (Node to continue to.) ### button_message Message with up to 3 buttons. Each button either opens a URL or branches the flow. With media it renders as a rich card, without it as a bubble with buttons. This is the button node to use. > Waits for the contact to reply before continuing. Needs the `dmButtons` capability on the target network. | Field | What it does | | --- | --- | | `text` · `text` · **required** | Message body. | | `buttons` · `messageButton[]` · **required** · max 3 | Each: {title, kind:"url"|"reply", url (when url), payload (when reply), next (branch of THIS button, reply only)}. | | `mediaUrl` · `string` | Public https URL of an attachment sent with the message. | | `mediaType` · `select` · one of: `image`, `video`, `audio`, `file` · default `image` | Kind of attachment. Networks differ: check dmAttachments in get_network_rules. | | `mediaButtonTitle` · `string` | Label of the link button used to deliver a document (mediaType "file"). On Instagram and Facebook a message with buttons only carries an image, so documents travel as a link button to their public URL. Defaults to the file extension. | Outputs: `next` (Continuation / fallback: no reply buttons, or an unmatched tap.) · `buttons[].next` (Branch taken when that specific reply button is tapped.) ### buttons Legacy node: text plus 1-3 link buttons. Does not branch. > Needs the `dmButtons` capability on the target network. Superseded by `button_message`; still runs, but prefer the newer one. | Field | What it does | | --- | --- | | `text` · `text` · **required** | Message body. | | `buttons` · `linkButton[]` · **required** · max 3 | Each: {title, url}. | | `mediaUrl` · `string` | Public https URL of an attachment sent with the message. | | `mediaType` · `select` · one of: `image`, `video`, `audio`, `file` · default `image` | Kind of attachment. Networks differ: check dmAttachments in get_network_rules. | | `mediaButtonTitle` · `string` | Label of the link button used to deliver a document (mediaType "file"). On Instagram and Facebook a message with buttons only carries an image, so documents travel as a link button to their public URL. Defaults to the file extension. | Outputs: `next` (Node to continue to.) ### reply_buttons Legacy node: text plus up to 3 reply buttons; waits for a tap and stores it. > Waits for the contact to reply before continuing. Needs the `dmButtons` capability on the target network. Superseded by `button_message`; still runs, but prefer the newer one. | Field | What it does | | --- | --- | | `text` · `text` · **required** | Message body. | | `replies` · `quickReply[]` · **required** · max 3 | Each: {title, payload}. Without payload the title is used. | | `variable` · `string` | Store the answer under this name. | | `mediaUrl` · `string` | Public https URL of an attachment sent with the message. | | `mediaType` · `select` · one of: `image`, `video`, `audio`, `file` · default `image` | Kind of attachment. Networks differ: check dmAttachments in get_network_rules. | | `mediaButtonTitle` · `string` | Label of the link button used to deliver a document (mediaType "file"). On Instagram and Facebook a message with buttons only carries an image, so documents travel as a link button to their public URL. Defaults to the file extension. | Outputs: `next` (Node to continue to.) ### carousel Horizontal carousel of cards. Instagram and Facebook only. > Needs the `carousel` capability on the target network. | Field | What it does | | --- | --- | | `elements` · `card[]` · **required** · max 10 | Each: {title, subtitle, imageUrl, buttons:[{title,url}] (max 3 link buttons per card)}. | Outputs: `next` (Node to continue to.) ### catalog Show the workspace catalogue as a carousel. Items come from the catalogue itself, not from the node — manage them with manage_catalog. > Needs the `carousel` capability on the target network. | Field | What it does | | --- | --- | | `category` · `string` | Free-text SEARCH, not an exact filter: it matches as a substring against item name, description or category. | Outputs: `next` (Node to continue to.) ### booking Book an appointment with buttons, without AI: service → (person, if the business lets people choose) → day → time → the required details, then the appointment is created (Google Calendar event included) and the flow continues. Services, hours and what to ask are configured in Appointments in the app (get_booking_settings), not here. Needs appointments in the plan (Blaze and up) and turned on. > Waits for the contact to reply before continuing. Needs the `dmButtons` capability on the target network. | Field | What it does | | --- | --- | | `serviceIds` · `string[]` | Restrict to these service ids. Empty = every bookable service. | Outputs: `next` (Taken once the appointment is booked.) · `noSlotsNext` (Taken when there is nothing to offer (no free slots, appointments off or not in the plan) or the person keeps writing instead of tapping. Falls back to next.) ### delay Pause the flow for a fixed number of minutes, then resume. | Field | What it does | | --- | --- | | `minutes` · `number` · **required** | Minutes to wait. | Outputs: `next` (Node to continue to.) ### delay_random Pause a random number of minutes between two bounds, so replies do not look automated. | Field | What it does | | --- | --- | | `minMinutes` · `number` · **required** | Lower bound, inclusive. | | `maxMinutes` · `number` · **required** | Upper bound, inclusive. | Outputs: `next` (Node to continue to.) ### question Ask something and wait for the answer, optionally validating and storing it. > Waits for the contact to reply before continuing. | Field | What it does | | --- | --- | | `text` · `text` · **required** | The question. | | `variable` · `string` | Store the answer under this name. | | `validate` · `select` · one of: `email`, `phone` | Require a valid email or phone. On a bad answer it resends retryText and asks again, then gives up and keeps whatever came so the user is never trapped. | | `retryText` · `text` | Message sent when validation fails. | | `timeoutMinutes` · `number` | Minutes to wait for an answer before taking the timeout branch. Without it, someone who never answers stays waiting forever and the flow ends there in silence — and not answering is the normal case, so this branch is usually the difference between capturing a contact and losing it. | | `timeoutNext` · `nodeRef` | Node to continue to when the wait runs out. Needed for timeoutMinutes to do anything. Typically a message that asks again. If the person answers before the time is up, this branch never fires. | Outputs: `next` (Node to continue to.) · `timeoutNext` (Taken when nobody answered within timeoutMinutes.) ### condition Branch on the user's last answer by keyword. | Field | What it does | | --- | --- | | `branches` · `branch[]` · **required** | Each: {keywords:[…], next}. Matching ignores case and accents, and hits on substrings. | Outputs: `branches[].next` (Branch whose keywords matched.) · `fallbackNext` (Taken when nothing matched.) ### follower Branch on whether the person follows the account. Instagram only exposes this; anywhere else it takes the yes branch. Outputs: `yesNext` (Follows, or unknown. Unknown counts as yes so nobody gets stuck.) · `noNext` (Only when Instagram explicitly confirms they do not follow.) ### ab_split Split runs between two branches at random and count each one, for real A/B stats. | Field | What it does | | --- | --- | | `percentage` · `number` · default `50` | Percentage going to branch A, 0-100. The rest go to B. | Outputs: `aNext` (Branch A.) · `bNext` (Branch B.) ### randomize Send one of several text variants at random, to avoid sounding repetitive. | Field | What it does | | --- | --- | | `texts` · `string[]` · **required** | Variants. Empty ones are ignored. | Outputs: `next` (Node to continue to.) ### tag Add tags to the contact. Silent: nothing is sent to the user. | Field | What it does | | --- | --- | | `tags` · `string[]` · **required** | Tags to add. They merge with existing ones, they do not replace them. | Outputs: `next` (Node to continue to.) ### field Set a custom field on the contact. Silent. | Field | What it does | | --- | --- | | `slug` · `string` · **required** | Field slug, from list_custom_fields. | | `value` · `string` | Literal value to store. | | `valueFromAnswer` · `boolean` · default `false` | Store the user's LAST answer instead of `value`. This is what makes question → field work: the engine does not interpolate variables, so without this flag nothing captured ever reaches the contact. | Outputs: `next` (Node to continue to.) ### subscribe Enrol the contact in a drip sequence. Silent. | Field | What it does | | --- | --- | | `sequenceId` · `string` · **required** | Sequence id, from list_sequences. | Outputs: `next` (Node to continue to.) ### handoff Hand the conversation to a human and STOP the bot for it. Terminal: no automation runs on that conversation again until someone clears it. > Ends the conversation: it has no outputs. | Field | What it does | | --- | --- | | `message` · `text` | Optional notice sent to the user. | | `assignMode` · `select` · one of: `auto`, `user`, `team` · default `auto` | auto lets Ignix route it; user or team forces an owner. | | `assignUserId` · `string` | Required when assignMode is user. | | `assignTeamId` · `string` | Required when assignMode is team. | ### ai Answer ONCE with the AI, using the workspace knowledge base and the contact's memory, then carry on with the flow. | Field | What it does | | --- | --- | | `instructions` · `text` | Extra steer for THIS point of the flow, e.g. "focus on booking a visit". | | `fallbackText` · `text` | Sent when the AI is unavailable or over its fair-use ceiling. | | `retrieveLimit` · `number` | How many knowledge passages to retrieve. | | `escalateOnUnknown` · `boolean` · default `false` | Take escalateNext when the AI could not answer from knowledge. | Outputs: `next` (Node to continue to.) · `fallbackNext` (Taken when the AI was unavailable.) · `escalateNext` (Taken when the user asks for a human, or on unknown if enabled. Wire it to a handoff node.) ### ai_agent Hand the conversation to the AI and let it answer EVERY incoming message, turn after turn, until it escalates. Use this instead of `ai` for open-ended conversations. > Waits for the contact to reply before continuing. | Field | What it does | | --- | --- | | `instructions` · `text` | Standing steer for the conversation. | | `fallbackText` · `text` | Sent when the AI is unavailable. | | `retrieveLimit` · `number` | How many knowledge passages to retrieve. | | `escalateOnUnknown` · `boolean` · default `false` | Escalate when the AI could not answer from knowledge. | Outputs: `escalateNext` (Taken when the user asks for a human, or on unknown if enabled. Without escalation the node keeps waiting for the next message.) ### comment_reply Post a PUBLIC reply to the comment that triggered the flow. Only does anything on comment triggers. > Needs the `commentReply` capability on the target network. | Field | What it does | | --- | --- | | `text` · `text` · **required** | The public reply. | | `texts` · `string[]` | Variants; one is picked at random per comment. Falls back to `text`. | Outputs: `next` (Node to continue to.) ### end End the flow. > Ends the conversation: it has no outputs. ============================================================================== SOURCE: https://ignix.social/help/broadcasts-and-sequences ============================================================================== # Broadcasts and sequences > **Where:** Automations > "Broadcasts" and Automations > "Sequences". A broadcast sends one message to many contacts at once. You can send it now or schedule it, and you can target contacts by tag. A sequence sends a series of messages spaced over time (a drip). Each step has its own delay: immediately, or after N minutes, hours or days. Contacts are enrolled by tag. ## Important network restrictions - Instagram and Facebook do not allow broadcasts. Their 24-hour messaging window makes it impossible. - Sequences cannot include media on any network. Broadcasts can. - Telegram and WhatsApp support broadcasts. WhatsApp requires a pre-approved template. ============================================================================== SOURCE: https://ignix.social/help/contacts ============================================================================== # Contacts > **Where:** Contacts. Contacts are the people who have written to you on any channel. For each contact you can see and edit their name, email, phone, company, notes, tags, the channels they have used and their last interaction. ## What you can do - Search and filter by tag. - Add or edit tags, individually or in bulk. - Block a contact. - Import contacts in bulk by pasting a list. - Export everything to CSV. - Create custom fields to store your own data on each contact. Contacts and messages are unlimited from the Blaze plan. ============================================================================== SOURCE: https://ignix.social/help/sparky-knowledge ============================================================================== # Teaching the AI assistant > **Where:** Sparky AI > Knowledge. This is where you teach the AI assistant about your business, so it can answer your customers. It is organised in three parts: "Your business": business name, a description of what you do, and your website. (That business name is also what your customers see on the booking page and in appointment emails.) "Voice & rules": the tone you want, reply length, emoji level, the assistant's name, your own instructions, and the message it should use when it does not know something. "Sources to learn from": your website URLs and uploaded documents (for example a PDF price list or an FAQ). ## Step by step 1. Go to Sparky AI > Knowledge. 2. Fill in your business name, description and website. 3. Set the tone and any rules you want the assistant to follow. 4. Add the pages and documents it should learn from. 5. Save. Knowledge learned from your websites refreshes automatically about every two weeks. You can also refresh it manually at any time. The assistant always answers in the language of the customer's last message, even when your knowledge base is written in a different language. The AI assistant is available on the Inferno plan, or by adding an AI seat to any other plan. The AI content studio and Autopilot are separate: they come included from the Blaze plan. ============================================================================== SOURCE: https://ignix.social/help/web-chat-widget ============================================================================== # Web chat widget for your site > **Where:** Sparky AI > Web chat. A chat bubble you embed on your own website, answered by the same AI assistant. Conversations from it arrive in your Ignix Inbox like any other channel. With Appointments on, the chat also shows a "Book an appointment" button that opens a picker (service, day, time, details) with no AI involved — and you can show this same chat on your public booking page (see "Appointments"). ## Step by step 1. Go to Sparky AI > Web chat. 2. Turn the widget on. 3. Set the title, greeting, colour, logo and assistant name. 4. Optionally restrict the domains where it may run (one domain per line). Leave it empty to allow any domain. 5. Copy the code snippet and paste it into your website just before the closing body tag. If you change the widget settings and your website still shows the old version, it is browser or CDN caching. Wait a few minutes or check in a private window. WHERE THE BUBBLE SITS (and what to do when it gets in the way) The bubble sits bottom right by default, which is also where most sites put their cart, their cookie bar or a WhatsApp button. Everything below is under Sparky AI > Web chat, in "Placement on your website": - Side: bottom right or bottom left. - Distance from the side and from the bottom, 0 to 200 px. Use this to lift the bubble above a fixed bar instead of moving it to the other corner. - Let visitors tuck the chat away: a small handle folds the bubble into a tab at the edge of the screen. It does NOT close the chat — one tap brings it back, it returns on the next page, and if someone writes to the visitor it opens again on its own. On by default. - Do not show it on phones: below 640 px the chat is not loaded at all. - Pages where it should not appear: one path per line, and * matches anything after it. For example /checkout* keeps it out of the whole checkout. - Use my own button instead of the bubble: hides our bubble completely, and you open the chat from any element of your site: Also available: Ignix.close(), Ignix.toggle() and Ignix.isOpen(). These work whether or not the bubble is hidden, so you can have both a bubble and a "contact us" link in your footer. Changes to placement apply immediately — the settings travel with the widget config, not with the snippet, so there is no need to touch your website again. You can also do all of this by asking a connected AI assistant, without opening the screen: "move the chat to the left", "keep it off the checkout", "hide it on mobile". See Integrations and custom actions. ============================================================================== SOURCE: https://ignix.social/help/analytics ============================================================================== # Analytics > **Where:** Analytics. ## Two tabs Posts: impressions, reach, engagement, likes, comments, shares and saves, over time. Includes your best post, a breakdown per network, a per-account view, best times to post, posting frequency versus engagement, and how engagement decays after publishing. You can export to CSV. Inbox: message volume, response time (average and median), a busiest-hours heatmap, your top accounts by conversation and where conversations come from. Follower counts are accumulated daily by Ignix, so follower history keeps growing the longer you use it. The rest of the data comes live from the networks and covers roughly the last 12 months. PDF REPORT. Click "Report" in Analytics to build a client-ready document: cover, executive summary and one section per page, each chart with a caption explaining it. You choose which sections go in — there are presets for "everything", "just content" and "just conversations" — and sections with no data are skipped, so ticking more than you have never leaves a blank page. Open it, check it, and use the Print button to save it as PDF. Brand sentiment is one of the sections you can include when your plan has AI. ============================================================================== SOURCE: https://ignix.social/help/brand-listening ============================================================================== # Brand listening and sentiment > **Where:** Inbox > Mentions (what people said) and Analytics > Inbox (the summary). Needs an AI-enabled plan. ## Three things at once SAVED SEARCHES. You tell Ignix what to watch for and it checks on its own. Only X and Reddit: no other network offers public search, and Ignix does not scrape. Go to Inbox > Mentions > "Manage searches" and add one: a name, the network, and what to look for. On X you can also tick "no retweets" and set a language without learning the syntax; if you know X operators ("exact phrase", OR, -is:retweet, from:user) you can type them straight into the query. Brand listening is an INFERNO feature: saved searches, mentions, sentiment, themes and reputation alerts all live there. Inferno includes 50 saved searches and up to 5,000 X mentions a month. If you downgrade, your searches are kept but paused, so nothing is lost if you come back up. Why only Inferno: X is the network where people complain, and it is the only one that charges per API call — every mention we bring you from X costs money. Other tools solve this by putting X behind their most expensive tier or by asking you to pay X yourself. We include X posting, DMs and inbox on every plan, and keep the listening on the top one. How often they run: about once an hour for a search that keeps finding things, and progressively less often for one that comes back empty, down to every six hours. This is deliberate — most searches are quiet most of the time, and it keeps your quota for what matters. What you do with a mention: read it, reply to it from Ignix, open it on the network, or mark it read. Replies go out through your connected account. SENTIMENT. Every comment, direct message, review and found mention is labelled positive, neutral or negative automatically. Analytics > Inbox shows the split for the period, a summary of what people are talking about, the recurring themes, and the most recent negative messages so you can act instead of just looking at a bar. Message text used for this is deleted after 90 days. ALERT. When negative messages in a day rise clearly above the usual average, Ignix warns you the same day. Configure it in Sparky AI > Settings: turn it on or off, set the minimum number of negative messages worth warning about (default 3), and choose which TEAM receives it. That last part matters in a company: whoever opened the account is rarely the person who handles reputation. With no team chosen, it goes to owners and admins. What Ignix does not do here: Instagram, TikTok, Facebook and LinkedIn have no public search API, so nobody can search them without scraping. What you get on those networks is everything that reaches your own accounts — comments, DMs and reviews — which is labelled and counted just the same. ============================================================================== SOURCE: https://ignix.social/help/reddit-radar ============================================================================== # Reddit Radar > **Where:** Reddit Radar (appears once you connect a Reddit account). Search Reddit for conversations about your topic, or browse a subreddit's feed, sorted by relevance, hot, top, new, comments or rising. Useful for finding threads worth joining and content ideas. ============================================================================== SOURCE: https://ignix.social/help/google-business-profile ============================================================================== # Google Business Profile > **Where:** Google Business Profile (appears in the menu once you connect a Google Business account). From here you can manage the listing itself, not just posts: business details, description, website and phone, photos, attributes, services, the menu, place actions, and verification status. You can also see and reply to reviews from the Inbox. ============================================================================== SOURCE: https://ignix.social/help/team-and-approvals ============================================================================== # Team, roles and approvals > **Where:** Organization > Team. ## To invite someone 1. Go to Organization > Team. 2. Enter their email and choose a role. 3. Send the invitation and share the link. ## Roles - Owner: full control, including billing. - Admin: everything except ownership. - Editor: creates and schedules content. - Approver: reviews and approves content before it goes live. - Viewer: read only. Approval flow: turn it on in Organization > Team. When it is on, posts created by editors wait in Approvals until an approver approves them. The approver can approve or reject with a reason. Rejected posts go back to the editor. Approvers get an email when something enters the queue, and the author gets one with the outcome (including the reason on a rejection). Team seats are available from the Scale plan (up to 3) and unlimited on Inferno. ============================================================================== SOURCE: https://ignix.social/help/workspaces ============================================================================== # Workspaces > **Where:** the workspace selector at the top of the sidebar. A workspace groups social accounts belonging to the same brand or client. It has its own knowledge base, its own AI assistant and its own web chat widget. Use several workspaces when you manage separate brands or clients and do not want their content, contacts or AI knowledge mixed. Switch workspaces from the selector at the top of the sidebar. Create and manage them from the same selector. ============================================================================== SOURCE: https://ignix.social/help/plans-and-billing ============================================================================== # Plans and billing > **Where:** Billing. Plans (monthly, USD). Unlimited contacts & messages from Blaze: - Spark, $19: 1 social account and 1,000 automated replies a month. - Blaze, $39: 3 social accounts, unlimited messages, AI content studio + Autopilot with 30 images a month, video with your own key, and online appointments (web chat, DM, booking page, Google Calendar). - Scale, $49: 5 social accounts, content AI with 80 images a month, team of up to 3 with roles and approval. - Inferno, $79: 10 social accounts, unlimited team, AI assistant included for one workspace (with 300 images a month), brand listening (50 saved searches, sentiment and alerts), and Sparky booking appointments in conversation. FAIR USE ON CONTACTS AND MESSAGES. From Blaze, contacts and messages are unlimited: we never charge per contact, and a post that goes viral never raises your invoice. The one thing we ask is that usage stays what it looks like — automations serving the audience your own accounts attract. A single exceptional month is normal use and we do nothing about it. If an organisation stays at an outlier volume two months running, we get in touch to check the plan still fits and propose one that does. We will not interrupt an automation that is already running: a viral post is when you need us most. The volumes and the exact wording are in the fair usage clause of our Terms. FAIR USE ON X. X is the only network that bills per API call, and Ignix passes that cost on to nobody — we absorb it. To keep it sustainable, two limits apply on X and only on X: 40 posts containing a link per month per account (X charges 13x more for those), and 5,000 listening mentions a month. Posting without a link, direct messages and the inbox are unlimited, as on every other network. THE SPARK LIMIT, IN DETAIL. Spark includes 1,000 automated replies a month. What counts toward it: each run of a chatbot flow (one person triggering an automation = 1), each broadcast recipient, and each contact enrolled in a sequence. What never counts: replying by hand from the inbox, scheduled posts, or the web chat. You can see the month's counter in Billing at any time. At 80% Ignix emails you a heads-up. At 100%, new automated conversations pause: conversations already in progress finish normally, and the inbox keeps working so nobody goes unanswered — you just answer by hand. Everything resumes automatically on the 1st of the next month, or instantly when you upgrade to Blaze, where contacts and messages are unlimited. ## Add-ons, available on any paid plan - Extra social account: +$6 per month each. - AI seat (enables the AI assistant on one more workspace): +$29 per month each. Annual billing costs 10 months instead of 12, a 17% saving. There is a 7-day free trial on the entry plan, Spark, and only when you pay monthly. Blaze, Scale, Inferno, every annual plan and all add-ons start straight away with no trial. The trial asks for a card, and three days before it ends Ignix emails you the date, the amount and a one-click link to cancel. To change plan, go to Billing and choose the new plan. To cancel or update your payment details, use the billing portal from the same page. When you downgrade to a plan with fewer accounts, Ignix asks you to choose which accounts to keep connected. The rest are disconnected, but nothing is deleted. If you cancel, you keep access until the end of the period you paid for. Cancelling is NOT the same as deleting. Cancelling stops the payments and leaves everything in place, so you can come back later. Deleting erases the account for good. If someone asks to "cancel and remove everything", point them at Deleting your account below — cancelling alone leaves their data with us. DELETING YOUR ACCOUNT > **Where:** Settings, at the bottom. Only the account owner sees it. ## You type the name of your organisation to confirm, and then - Every subscription is cancelled that same day. No further charges. - Your social accounts are disconnected, so Ignix loses all access to them. - Your posts, conversations, contacts, automations, knowledge and files are erased from our database. - Everyone on the team is signed out and cannot get back in. It is immediate and permanent. There is no trash bin, no grace period and no way for support to restore it. Anything worth keeping — reports, exported data, media — has to be downloaded first. ## Two things survive on purpose - Invoices, which are held by Creem, our merchant of record, because tax law requires them to keep them. Download them from the billing portal first. - Posts already published on a social network. Deleting the Ignix account does not delete what is already live on Instagram, LinkedIn and so on; those have to be removed on each network. If the owner has left the company or cannot access the account, email legal@ignix.social and we will carry out the deletion. That is also how to exercise the right to erasure under GDPR; we answer within 30 days. ## If a payment fails Your plan is not cut off at the first decline: Stripe retries the charge for a few days and a red notice in the app points you to update the card from Billing (or from the email link, no login needed). If the charge recovers, everything continues untouched. If the retries run out, the subscription is cancelled and connected accounts are disconnected; your drafts and settings are kept. ============================================================================== SOURCE: https://ignix.social/help/settings ============================================================================== # Settings > **Where:** Settings. - Time zone: the zone used by the calendar, the queue and all scheduling. - Notifications: choose whether to receive email and push notifications, for example when a conversation is assigned to you. - Language: change the interface language from the selector at the bottom of the sidebar. - Connect an AI assistant (MCP): see the section below. - Delete account: at the bottom, owner only. See Deleting your account in Plans and billing. Ignix can be installed as an app on your phone or computer. Open it in your browser and use your browser's install option, or the banner Ignix shows. ============================================================================== SOURCE: https://ignix.social/help/integrations ============================================================================== # Integrations and custom actions > **Where:** Integrations. Connect an online store so the AI assistant can look up live product and order data when a customer asks. You can also define your own custom actions: give the AI a URL to call, with its parameters, and it will use it during conversations when it is relevant. Each action can be tested before you enable it. ============================================================================== SOURCE: https://ignix.social/help/mcp ============================================================================== # Connect an AI assistant (MCP) > **Where:** Settings → MCP server. Ignix can be driven by an AI assistant. Once connected, you can ask Claude, ChatGPT or a similar assistant things like "plan next week for Instagram", "generate an image for this post and schedule it on Friday at 2pm" or "how did last month go?", and it does the work inside your Ignix account. There are two ways to connect, and Settings shows both with the exact address. 1) Sign in with Ignix (recommended) For any assistant that supports remote MCP servers. You add the Ignix address as a connector, the assistant opens Ignix, you sign in, choose the workspace and approve. There is no key to copy or store. You can revoke that access whenever you want, and an assistant only gets the permissions you approved: read-only access cannot publish. 2) With an API key For tools that cannot open a browser: automation platforms such as n8n or Make, your own scripts, or a server. Create the key in Settings and send it in the Authorization header. The key belongs to the whole organization and does not expire, so treat it like a password and revoke it if it leaks. What the assistant can do: publish and schedule on any connected network, generate images with AI, read analytics, work the inbox, create or edit chatbot automations, and manage appointments: see how they are set up, check free slots, book one that came in by phone (the customer gets the confirmation email), list the upcoming ones and cancel. Video is the one exception, and it is worth knowing before you ask for one: generating video needs an API key from a provider (Runway, Veo 3, Kling, or HeyGen, Creatify and Synthesia for avatars) added in Settings first. Until someone adds one, the assistant will tell you there is no provider available rather than produce a video. Images need nothing: they are included in your plan. It can also read your posting style — the brand colours, how your posts are built and how you write on each network — so what it writes and designs matches the rest of your feed, and re-derive it from your published posts when it has gone stale. Actions that reach a real person — sending a message, replying to a comment or a review — are marked so your assistant asks you for confirmation first. What it cannot do: connect or disconnect social accounts, change your plan, or see anything outside the workspace you approved. ============================================================================== SOURCE: https://ignix.social/help/mcp-reference ============================================================================== # MCP server reference Ignix exposes 138 tools over the Model Context Protocol, so an AI assistant can publish, answer messages, read analytics and build automations on your behalf. This page lists every one of them and is generated from the server's own registry. ## Connecting The server is remote and speaks Streamable HTTP over HTTPS, with OAuth 2.1 and a consent screen where you choose which workspace the assistant may reach. In the app, the address and the token live in **Settings → MCP server**. ```json { "mcpServers": { "ignix": { "url": "https://app.ignix.social/api/mcp" } } } ``` ## Reading this list Each tool is marked **read-only** (only reads), **writes** (changes something in Ignix) or **destructive** (deletes, unpublishes or reaches a real person). Assistants are expected to confirm destructive calls with you first. ## Accounts and workspaces | Tool | What it does | Access | | --- | --- | --- | | `list_accounts` | List the social accounts connected to this organization. | read-only | | `list_workspaces` | List the workspaces (brands / clients) of this organization. | read-only | | `check_account_health` | List connected accounts that need attention: token expired or about to expire (`reconnect` / `expiring`, the human must reconnect them in Ignix), or messaging restricted by Meta on a Facebook Page (`restricted`: automations for it are paused and resume by themselves once Meta lifts the restriction; check the Page status in Meta Business Suite). | read-only | | `get_network_rules` | Publishing and automation rules for a social network: character limit, media requirements, supported content types (reel, story, carousel, thread), and which inbox automations that network allows. | read-only | | `get_organization` | Organization name, timezone and plan. | read-only | | `list_account_summary` | One-shot overview: every connected account with how many posts it has scheduled and when the next one goes out. | read-only | | `sync_accounts` | Re-read the accounts from the networks. | writes | | `create_workspace` | Create a workspace (a separate brand or client, with its own accounts, library and knowledge) or rename an existing one.. | writes | | `list_account_media` | Images and videos taken from what the accounts have already published (native posts included). | read-only | ## Publishing | Tool | What it does | Access | | --- | --- | --- | | `list_posts` | List posts of the organization (drafts, scheduled, published, failed) with their status, target accounts and media.. | read-only | | `get_post` | Full detail of one post, including per-network options and failure detail.. | read-only | | `create_post` | Create a post for one or more social accounts. | writes | | `update_post` | Edit an existing post (typically a draft or a scheduled one): copy, media, target accounts, schedule. | writes | | `validate_post` | Dry run: check copy and media against every target network (character limits, media requirements, mandatory options) WITHOUT creating anything. | read-only | | `schedule_post` | Move an existing scheduled post to another date and time.. | writes | | `delete_post` | Delete a post from Ignix and from the scheduler. | destructive | | `unpublish_post` | Remove an already published post FROM THE SOCIAL NETWORK. | destructive | | `retry_post` | Send a failed post to the network again, keeping its content and targets.. | writes | | `duplicate_post` | Create a draft copy of an existing post, ready to edit and reschedule.. | writes | | `recycle_post` | Republish a post that already performed well, scheduling it in the next free queue slot.. | writes | | `suggest_publish_times` | Next free slots in the organization's posting queue, in its timezone. | read-only | | `list_pending_approvals` | Posts waiting for review when the approval workflow is enabled for this organization.. | read-only | | `review_post` | Approve a post awaiting review (it is then scheduled or published according to its intent) or reject it back to draft with a reason.. | writes | | `get_network_options` | Every option a network accepts in `networkOptions` when creating a post: key, type, whether it is required, and the exact accepted values (Instagram contentType, YouTube privacy, TikTok consent, Pinterest board, Reddit flair…). | read-only | | `get_network_choices` | Values that only the network can give for a specific account: Pinterest boards, the subreddits the account can post to, Reddit flairs of a subreddit, YouTube playlists, the TikTok privacy levels that account actually allows, the Facebook Pages the account manages, and the LinkedIn company pages it administers. | read-only | | `get_subreddit_rules` | Posting rules of a subreddit plus Reddit site-wide rules. | read-only | | `get_posting_queue` | Recurring weekly slots of the organization: the grid used by `useQueue` and by suggest_publish_times, in the organization timezone.. | read-only | | `set_posting_queue` | REPLACE the weekly grid of recurring slots. | writes | | `bulk_create_posts` | Create many posts for the same accounts in one call. | writes | | `attach_media_to_post` | Add an already hosted image/video URL to a post that exists. | writes | | `suggest_post_idea` | Propose a ready-to-publish post idea for a given network, based on the brand and limited to what this organization can actually produce (it will not suggest an AI video if no video provider is configured).. | writes | | `get_top_posts` | Ranking of published posts by engagement in the period, with their metrics, engagement rate and caption. | read-only | | `get_posting_cadence` | How many posts per week each network gets and the engagement rate at that cadence — the data behind "should we post more or less?".. | read-only | | `list_library_posts` | Content already published on the networks, INCLUDING posts published natively outside Ignix, with its media. | read-only | ## Media and AI content | Tool | What it does | Access | | --- | --- | --- | | `edit_image` | Edit an image you already have: change the background, add or remove an object, restyle it, make a variation. | writes | | `generate_image` | Generate an image from a text prompt and return a durable public URL ready to pass to create_post as media. | writes | | `get_image_quota` | How many AI images this organization has used this month and how many it has left. | read-only | | `list_media_providers` | Video and avatar-video providers that are wired AND have a key configured by this organization. | read-only | | `generate_video` | Start an AI video generation job (text-to-video, image-to-video, or an avatar reading a script). | writes | | `get_media_job` | Status of a video generation job. | read-only | | `list_avatar_options` | Avatars and voices available in an avatar provider with this organization key. | read-only | | `upload_media` | Put a file that lives on the user's machine into durable Ignix storage and get back a stable https URL. | writes | | `import_media` | Download a public URL and re-host it on durable Ignix storage, returning a stable URL usable as post media or as the file of a chatbot flow node. | writes | | `list_library_media` | Images and videos already generated or uploaded by this organization, newest first. | read-only | | `write_caption` | Write a post caption from an idea, using this organization's brand voice (business description, tone and knowledge base). | writes | | `adapt_caption` | Rewrite an existing text in the native style and length of a given network (a LinkedIn post is not an X post). | writes | | `translate_caption` | Translate a text naturally into another language, keeping tone, emojis and hashtags.. | writes | | `suggest_hashtags` | Up to 5 relevant hashtags for a text, mixing popular and niche ones (few and relevant beats many).. | writes | | `plan_content` | Plan a piece of content end to end: caption plus, for each slide, its idea and a detailed art-directed image prompt with a shared visual style. | writes | ## Inbox | Tool | What it does | Access | | --- | --- | --- | | `suggest_first_comment` | Write the first comment to go under a post: the right place for links, an engagement question or extra hashtags.. | writes | | `list_conversations` | Conversations from the unified inbox: direct messages from every connected network plus the website chat. | read-only | | `get_conversation` | Message history of a conversation, oldest first. | read-only | | `send_message` | Send a message in an existing conversation. | destructive | | `start_conversation` | Open a direct message with someone who has not written first. | destructive | | `update_conversation` | Change the pipeline stage of a conversation, mark it read, or escalate it to a human (which silences the bot on that thread and notifies the team).. | writes | | `list_comments` | Published posts that have comments, newest first. | read-only | | `get_comment_thread` | Comments on a published post, with author and text.. | read-only | | `reply_to_comment` | Reply publicly to a comment, or send a private direct message to its author (`private: true`, Instagram and Facebook only, within 7 days of the comment). | destructive | | `moderate_comment` | Hide a comment from the public (or unhide it). | destructive | | `list_reviews` | Reviews received (Google Business Profile and other networks that support them), with rating, text and whether they have been answered.. | read-only | | `reply_to_review` | Publish a public reply to a review. | destructive | | `list_tickets` | Conversations promoted to support tickets, with number, subject, priority and stage.. | read-only | | `list_saved_replies` | Canned replies the team has saved. | read-only | | `preview_automation` | Read a flow the way a customer would experience it: the sequence of messages, buttons and branches. | read-only | | `save_reply_template` | Maintain the saved replies the team uses in the inbox. | writes | | `create_ticket` | Promote a conversation to a support ticket, with number, subject and priority, so it stops living only in the inbox. | writes | | `create_comment_to_dm` | The classic growth automation: someone comments a keyword on a post and automatically receives a direct message. | writes | | `manage_welcome_message` | The message someone receives the first time they write to an account. | writes | | `list_mentions` | Mentions found outside the organization's own posts, by its saved searches on X and Reddit, newest first. | read-only | | `reply_to_mention` | Reply on the network to a mention found by a saved search. | writes | ## Contacts | Tool | What it does | Access | | --- | --- | --- | | `list_contacts` | Contacts of the CRM: people who have interacted through any channel, with their tags, email and subscription state.. | read-only | | `get_contact` | Full detail of a contact: channels they use, tags, custom fields, notes and last interaction.. | read-only | | `create_contact` | Add a contact to the CRM. | writes | | `update_contact` | Edit a contact: name, email, company, notes, tags, subscription or blocked state. | writes | | `set_contact_field` | Write a value into one of the custom fields defined for this organization (list them with list_custom_fields).. | writes | | `list_custom_fields` | Custom fields defined for contacts, with their slug and type.. | read-only | | `create_custom_field` | Define a new field for contacts (text, number, date or a list of options) so the bot and the team can store data about each person.. | writes | ## Appointments | Tool | What it does | Access | | --- | --- | --- | | `get_booking_settings` | How appointments are set up in this workspace: services (duration, buffers, price with its currency, who does them), people and rooms (hours, days off, spots), what is asked when booking, the rules (slot step, minimum notice, horizon, reminders, cancellation policy, currency), whether Google Calendar is connected, and the public booking page URL. | read-only | | `get_booking_availability` | Free slots for a service from a given day, honouring hours, days off, spots, buffers and what is already in Google Calendar. | read-only | | `create_appointment` | Book an appointment on behalf of the business (for example one that came in by phone). | writes | | `list_appointments` | Upcoming appointments booked through Ignix (web chat, DM, Sparky, booking page or this MCP). | read-only | | `cancel_appointment` | Cancel an appointment booked through Ignix by id (from list_appointments). | destructive | ## Automations | Tool | What it does | Access | | --- | --- | --- | | `get_automation_usage` | How many times each chatbot flow ran in the period, and which are active. | read-only | | `list_automations` | Automation flows of this organization: name, trigger, whether they are active and how many times they have run.. | read-only | | `get_automation` | Detail of a flow, including its node graph — useful to explain what the bot answers and where it escalates to a human.. | read-only | | `set_automation_active` | Enable or disable an automation flow. | writes | | `list_broadcasts` | Mass messaging campaigns sent or scheduled from the inbox, with their state.. | read-only | | `list_sequences` | Timed message sequences (drip campaigns) and their steps.. | read-only | | `search_knowledge` | Semantic search over everything this business has taught its AI: website, uploaded documents, social posts, manual notes. | read-only | | `get_brand_profile` | How this business describes itself and how its AI should sound: business name, description, tone, agent name, standing instructions, and which knowledge sources are loaded. | read-only | | `learn_brand_style` | Re-reads the posts this workspace's accounts have already published and updates the posting style returned by get_brand_profile: brand colours with their role, how the posts are built, and how the brand writes on each network. | writes | | `list_catalog` | Catalogue of products/services this business has loaded, with price and description. | read-only | | `get_automation_node_types` | The FULL specification of every node and trigger a flow can use: what each one does, its exact fields with types and accepted values, its outputs (which branch goes where), and whether the chosen accounts support it. | read-only | | `list_automation_templates` | Ready-made flows (welcome menu, lead capture, qualify and hand off, follower gate, comment coupon, drip opt-in), each with the COMPLETE graph it would build and the trigger it would use. | read-only | | `create_automation_from_template` | Instantiate a template as a new flow, adapted to this business. | writes | | `create_automation` | Create a chatbot flow. | writes | | `update_automation` | Edit a flow: name, trigger, target accounts or the whole node graph. | writes | | `duplicate_automation` | Copy an existing flow, graph and all, so you only have to change what differs — typically the keyword and the post. | writes | | `delete_automation` | Delete a flow permanently. | destructive | | `create_broadcast` | Create a mass message to the CRM contacts of one account. | destructive | | `send_broadcast` | Send a broadcast NOW to every recipient. | destructive | | `cancel_broadcast` | Cancel a scheduled broadcast, or delete it entirely with `remove: true`.. | destructive | | `create_sequence` | Create a timed message sequence (drip): each step goes out after its delay. | writes | | `update_sequence` | Change the state of a drip sequence.. | writes | | `enroll_in_sequence` | Enroll a SEGMENT of contacts in a drip sequence: those carrying the given tags, or every subscriber of that account if no tag is given. | destructive | | `teach_knowledge` | Add text to this workspace's knowledge base: a policy, an FAQ, prices, how a process works. | writes | | `manage_catalog` | Maintain the product/service catalogue the assistant shows customers. | writes | | `list_quick_automations` | The simple automations built without the flow editor: someone comments a keyword and gets a direct message, or replies to a story and the bot answers.. | read-only | | `get_bot_setup` | Persistent menu (Facebook), ice breakers (Instagram) and bot commands (Telegram) configured on an account. | read-only | | `set_bot_starters` | Configure what a customer sees before writing: the persistent menu on Facebook (up to 3 entries) or the ice breakers on Instagram (up to 4 questions). | writes | | `get_brand_sentiment` | INFERNO ONLY. | read-only | ## Analytics and listening | Tool | What it does | Access | | --- | --- | --- | | `get_analytics` | Aggregated performance for the period: totals per metric (impressions, reach, likes, comments, shares, saves, followers…), the same totals for the previous period so you can state growth, and a per-network breakdown. | read-only | | `get_best_times` | Weekday × hour engagement grid built from this organization's own history, in its timezone. | read-only | | `get_follower_growth` | Follower evolution per account and in total, from the daily snapshots Ignix stores. | read-only | | `get_engagement_trend` | Daily engagement and impressions over the period, plus whether the second half is doing better or worse than the first. | read-only | | `get_audience` | Audience breakdown by age, gender, country and city. | read-only | | `get_inbox_analytics` | Messaging performance: messages received and sent, share answered by automation, average and median response time, unread count, and the busiest accounts.. | read-only | | `manage_saved_searches` | INFERNO ONLY. | writes | | `search_reddit` | Search Reddit, or read the feed of a subreddit, through a connected Reddit account. | read-only | | `build_report_link` | Link to the analytics report laid out as a document — cover, executive summary and one section per page — ready to save as PDF from the browser. | read-only | | `get_x_usage` | X is the only network billed per API call, so it is the only one with monthly allowances: posts containing a link (X charges 13x more for those) and brand-listening mentions. | read-only | ## Google Business, WhatsApp and web chat | Tool | What it does | Access | | --- | --- | --- | | `list_whatsapp_templates` | Message templates approved by WhatsApp for an account, with their status. | read-only | | `manage_reputation_alerts` | Read or change the reputation rules: the warning that fires when negative messages spike above the usual daily average, and what happens when a new review arrives — alert the team at or below a star rating, and optionally reply automatically at or above one. | writes | | `manage_whatsapp_templates` | Message templates are what WhatsApp requires to write to someone outside the 24h window, and Meta has to approve them first — a new one starts as PENDING and cannot be used until it is APPROVED. | writes | | `manage_whatsapp_profile` | The business card customers see on WhatsApp: the "about" line, description, email, websites, address and business vertical.. | writes | | `manage_whatsapp_flows` | Flows are the forms that open inside WhatsApp (booking, qualifying, ordering). | writes | | `get_gbp_listing` | Everything on the business listing: its locations, the details (description, website, phone), the attributes Google offers for that category, the services, the booking/order links and the food menu. | read-only | | `update_gbp_listing` | Change the description, website or phone, and switch on or off the boolean attributes Google offers for that category (wheelchair access, outdoor seating, delivery…). | writes | | `manage_gbp_photos` | The photos on the listing. | writes | | `manage_gbp_offerings` | What the business sells and how people act on it: the service list, the action links (book, order, reserve) and the food menu. | writes | | `manage_gbp_verification` | An unverified listing does not show up properly in Search or Maps, so this is usually the first thing to fix. | writes | | `manage_web_chat` | The chat bubble the customer embeds on their own website. | writes | ## Team | Tool | What it does | Access | | --- | --- | --- | | `get_connect_url` | Return a link the human can open to connect a new social account, or to reconnect one whose token expired. | read-only | | `list_writing_assets` | Hashtag sets and reusable text snippets the team has saved. | read-only | | `save_writing_asset` | Store a reusable hashtag set or text snippet so the team (and future posts) can use it.. | writes | | `engage_on_x` | Act on X (Twitter) from a connected account: retweet a post, bookmark it, or follow an account. | destructive | | `list_team` | Who is in this organization, with their role, plus the sub-teams and the pending invitations. | read-only | ## Everything else | Tool | What it does | Access | | --- | --- | --- | | `manage_style_examples` | Style material the customer SUPPLIES from accounts that are not connected to Ignix: captions, video transcripts or images from their old TikTok, another brand of theirs, anything they want the style learned from. | writes | ============================================================================== SOURCE: https://ignix.social/help/troubleshooting ============================================================================== # Troubleshooting "My post failed." Open the post in Posts. The failure reason from the network is shown on it. The most common causes are an expired token (reconnect the account), media that does not meet the network's requirements, and text over the network's character limit. "An account says it needs reconnecting." The network has expired or revoked the access token. Go to My Accounts and connect that account again. Nothing is lost. "I cannot connect an account, or the wrong profile gets connected." Log out of that social network in your browser, then connect again from My Accounts. The network reuses whatever session is already open. "Instagram will not let me post." Instagram requires a Business or Creator account, linked to a Facebook Page. Personal accounts cannot publish through any API. "My Instagram image is rejected or gets cropped." Instagram feed images must be between 0.8 (4:5) and 1.91 (landscape). Use the crop button in the composer to fix it, or publish it as a Story. "TikTok rejects my post." TikTok requires a privacy level and both consent confirmations. Fill in the TikTok options in the composer before scheduling. "The AI is not answering my customers." Check three things: that the AI assistant is enabled for that workspace (it is included on Inferno, or via an AI seat), that the knowledge base has your business information, and that no human has taken over the conversation. A conversation a human has replied to stops being answered by the AI until you mark it as handled. "The AI answered in the wrong language." It answers in the language of the customer's last message. If a customer switches language mid-conversation, the AI follows them from that message on. "My AI image or video prompt was rejected." Prompts are checked against our content policy before generation. Rewrite the prompt without the rejected content and try again. "I hit my AI image limit." Image generation has a monthly allowance per plan. It resets each billing month. "My web chat changes are not showing on my website." It is caching. Wait a few minutes or open your site in a private window. "I need help with something not covered here." Write to support@ignix.social. ============================================================================== SOURCE: https://ignix.social/help/limits ============================================================================== # What Ignix does not do ## Be honest with customers about these - It does not publish to WhatsApp as a post. WhatsApp is a messaging channel. - It does not send broadcasts on Instagram or Facebook. Their 24-hour messaging window does not allow it. - It does not send media inside sequences (broadcasts can carry media). - It does not manage inboxes for TikTok, Pinterest or Snapchat. Pinterest and Snapchat do not offer inbox access; TikTok only opens it to business accounts, and Ignix does not support it yet. - It does not reply privately to comments outside Instagram and Facebook. - It does not generate adult, sexual or NSFW content, deepfakes or face swaps. See the Acceptable Use Policy. - It does not run ads or manage ad campaigns. - It does not search Instagram, TikTok, Facebook or LinkedIn for mentions. Those networks have no public search API and Ignix does not scrape. On them you see everything that reaches your own accounts, labelled and counted the same way. ============================================================================== SOURCE: https://ignix.social/help/affiliate-program ============================================================================== # Partner (affiliate) program Anyone can recommend Ignix and earn **30% of every payment their referrals make, for as long as those customers stay subscribed**. There is no 12-month cut-off and no cap. - Free to join, no minimum audience. - 90-day attribution window: if someone clicks your link and subscribes within 90 days, the referral is yours. - Your commission follows what each customer actually pays, so extra social accounts and AI seats they add later count too. - Tracking and payouts are handled by Creem, our merchant of record. - Prices exclude VAT: commission is calculated on the plan price, not on tax. Where to sign up: the Affiliates page at www.ignix.social/affiliates has the full terms, a calculator and the join link. It is also linked from the main menu of the website and from the bottom of the sidebar inside the app. You do NOT need to be a customer to join.