Almost every connection problem comes down to one of three things: the domain allowlist in your AI tool's settings, a setting change that has not reached the conversation you are testing in, or a plan restriction that looks like a technical failure.
The domain allowlist is not configured. In Claude, open your settings, go to Capabilities, turn on code execution and network egress, then set the domain allowlist to allow specific domains and add tools.flipperforce.com. On Team and Enterprise plans an organization owner has to do this. See How do I connect Claude to FlipperForce? for the full setup.
You most likely changed a setting, and the change did not apply to a conversation that was already open. Close it, start a brand new conversation, and try again. This is the most common false alarm we see.
Uploading a file is a two-destination process. The record goes to our API, but the file itself goes to our storage provider. Add flipperforce-prod.nyc3.digitaloceanspaces.com to the allowlist as well, then start a new conversation.
The key is invalid or expired, or the subscription it belongs to has lapsed. Check your subscription status first, then request a replacement key through the integrations page.
This is usually not a broken integration. It normally means your plan does not include that module, or your role in the workspace does not permit the action. Expense Tracker, Photo Log, Companies and Contacts, and Material Catalog need an All-in-One plan. Project Updates need a Teams or Business plan. Ask your agent to show the message and reason the API returned rather than retrying.
The request was missing a required field or had a value in the wrong format. Ask your agent to show you the exact payload it sent.
Calls are going out too fast. Ask the agent to slow down and retry with backoff.
The Agent Guide is not in the Project, or it is not being read. Confirm it is uploaded, and add a line to your Project instructions telling the agent to read the guide before making calls.
Your Project instructions are missing the safety rules. The instructions block in our setup kit makes the agent read-only by default and requires it to show you every change before saving. Paste it into the Project's custom instructions field.
The agent almost certainly added up one page of results instead of using the totals the API returns. Our list endpoints calculate totals across everything that matched before pagination. Tell the agent to use those totals and to follow pagination cursors to the end rather than assuming the first page is the whole set.
Too many individual calls. For anything that reads across a lot of records, ask the agent to write and run a script instead of making calls one at a time.
Email support@flipperforce.com or start a chat from inside FlipperForce. Tell us which step you are on and what the agent showed you, and we will pick it up from there.
