How to set up Ignix and connect it to Claude

Sign up, confirm the email, and you are in. There is a short guided tour the first time that points out the main sections; you can skip it and replay it later from Settings, and it is per person, so replaying it does not reopen it for your team.

Nothing needs configuring before you can publish. Everything in Settings is optional except the timezone, which is worth a look now: it is what the calendar, the queue and every scheduled time use, and fixing it after you have queued a week is more annoying than setting it before.

My Accounts is the first entry in the menu. Click “Connect a new account”, pick the network, log in on the network’s own page and approve the permissions. You come back and it is in the list.

Three things catch people out, and all three are the network’s rules rather than ours. Instagram needs a Business or Creator account — a personal one cannot publish through any API, ours included. Facebook connects Pages, not your personal profile: you log in as yourself, but what gets connected is the Page you administer. LinkedIn works the same way with company pages.

And if the wrong profile ends up connected, the cause is almost always the browser: the network reuses whichever session is already open. Log out of that network in your browser, then connect again.

Before handing anything to an assistant, publish one post yourself. Not ceremony — two reasons.

The first is that the composer tells you things you will want to know: it checks the image proportions against what each network accepts, counts the hashtags, and shows you a preview per network before anything goes out. Watching it catch something once is the fastest way to understand what it is doing for you later.

The second is that the analytics need history. The best-times heatmap, the top posts, the posting cadence — they are all built from what you have actually published. On day one they are empty, and that is not a bug.

This step is optional, and skipping it does not break anything. Publishing, scheduling and analytics all work without it. If AI is not what you came for, go straight to step five, or stop at step three and use Ignix as a scheduler — plenty of people do.

What it turns on is the answering. Sparky is the AI that replies to your DMs, your comments and your website chat, and it replies from what you tell it. An empty knowledge base produces an assistant that is polite and useless, which is worse than none.

The minimum is your business name, what you do, and your website — from the site it reads and learns your public pages on its own. If you sell something, add prices and policies too: those are the questions that actually arrive.

It also feeds the writing. When an assistant drafts a caption later it reads the same knowledge, so it knows what you sell and does not invent a product you do not have.

Open Settings → MCP server in Ignix. It shows the address to use and the two ways to connect. Copy the address.

In Claude, go to Customize → Connectors, click the “+” and then “Add custom connector”, paste the address and click Add. Claude opens Ignix, you sign in, you choose which workspace it gets and you approve. There is no key to copy anywhere, and you can revoke it whenever you want. Custom connectors work on the free plan too, though a free account can only have one at a time.

You only do this once. The connector belongs to your Claude account, not to the machine you added it on, so it turns up on your phone by itself — which is where a surprising amount of this ends up happening.

If you are on a Team or Enterprise plan, an owner adds it once in Organization settings → Connectors and everyone else then sees it in their own Connectors list with a Connect button.

The second way is for tools that cannot open a browser — n8n, Make, your own scripts. Create an API key in the same Settings page and send it in the Authorization header. That key belongs to the whole organization and does not expire, so treat it like a password.

Start with something you can check. “What did my last ten posts do?” is a good first request: it is read-only, the answer is verifiable, and it tells you the connection works.

Then try something that writes. “Plan next week for Instagram: four posts about our summer range, generate the images, and schedule them at my best times.” That single sentence uses the knowledge base, the image generator, the best-times grid and the scheduler, and you get a calendar to review before anything publishes.

And once you have images, “take that last one and put the product on a marble surface with daylight from the left” edits it rather than generating a new one from scratch.

The one people do not expect is building automations by describing them. “When someone comments GUIDE on my last reel, send them the link by DM, wait a day, and follow up if they have not opened it” is a sentence, and it comes back as a flow — trigger, message, wait, condition, branch — that you can open in the visual builder and change like any other.

It does not guess at what a flow can contain: it reads the full specification of every node and trigger from Ignix first. And a flow it builds is created switched OFF. You read it back in plain language, and it only starts answering people when you say so.

And none of it has to be typed. Because the connector follows your account onto your phone, and because Claude takes voice, a week of posts or a whole comment-to-DM flow is something you can dictate walking down the street — and find waiting for you, built and switched off, when you next sit down. It is how we use it ourselves: the automations and the posts get made from a phone, while the laptop is busy with something else.