Connecting
The sign-in page reads Connection request invalid
The sign-in page reads Connection request invalid
The page was opened without the details your assistant sends. Close the tab and start the connection from the assistant’s connector settings.
The sign-in page reads Connection not allowed
The sign-in page reads Connection not allowed
Fanaura did not recognize the assistant’s return address. Check the allowed return addresses. If your client uses a hosted address that is not listed, email support@fanaura.com with the exact URL.
My sign-in code did not arrive
My sign-in code did not arrive
Check spam, then tap Use password instead on the sign-in page.
The assistant connected to the wrong Fanaura account
The assistant connected to the wrong Fanaura account
Remove Fanaura in the assistant’s settings and connect again. On the Fanaura page, tap Use a different account before Allow access. If the assistant reconnects without showing the page, email support@fanaura.com so Fanaura can cancel the old sign-in.
My editor says the server needs login, and nothing opens
My editor says the server needs login, and nothing opens
Some editors only start sign-in when you click the server in their MCP panel. In Claude Code, run
/mcp and choose Authenticate. In Gemini CLI, run /mcp auth fanaura.Using the tools
The assistant says a Fanaura tool does not exist
The assistant says a Fanaura tool does not exist
Assistants save the tool list when you connect. Start a new chat. If that does not help, disconnect and reconnect Fanaura.
The assistant asks me to confirm before publishing
The assistant asks me to confirm before publishing
Tools that publish or change a journey are marked destructive, so the assistant may show its own approval card before it runs them. Fanaura cannot turn that card off. Approve it once. In Claude, choose Always allow for the tool if you do not want the card again.
fanaura.start_journey creates a new draft only and is not marked destructive. Read tools are read only.The journey saved but did not go live
The journey saved but did not go live
The reply names the reason. The full list is in Errors and limits. The most common reason is that Instagram is not connected.
The keyword is live but nobody gets a DM
The keyword is live but nobody gets a DM
Check that the person commented the exact keyword as one word. Confirm Instagram is still connected by asking “Is my Instagram connected?” If the answer says it needs a reconnect, ask “Connect my Instagram.” If the journey is followers only, people who do not follow you will not get the link.
A contact I expected is missing
A contact I expected is missing
Search with a shorter fragment, such as “Find contacts named Jor”, or search by Instagram handle. Contacts belong to the Fanaura account the assistant is signed in to, so check that it is the right account.
get_contact says more than one contact matched
get_contact says more than one contact matched
Two contacts share that detail. Ask the assistant to search first, then pick one by its contact ID.
Audience numbers look low for a long range
Audience numbers look low for a long range
Each breakdown reads up to 5,000 rows. When the result says
truncated: true, ask for a shorter range.I hit the rate limit
I hit the rate limit
The limit is 120 requests per minute per user. Wait a minute. If a script or agent loops, add a delay between calls.
Still stuck
Email support
Include the assistant you use, the prompt you sent, and the time it happened.
Check the server
Confirm the server answers with a single
curl command.