Developer overview
Updated October 10, 2026
InfluenceBot can work with your own systems and no-code tools. Everything for developers lives in Settings, and the people who set it up are usually workspace owners and admins.
What you find in Settings
- API keys: keys that let your systems call the InfluenceBot API for this workspace. See Create an API key.
- Webhooks: send InfluenceBot events to your own HTTPS endpoints. See Receive webhooks.
- API docs: the API reference. See Use the public API.
- Zapier, Make & n8n: no-code apps and their status. See Zapier, Make and n8n.
- Your AI provider keys: use your own OpenAI, Anthropic or Gemini account for AI text, if enabled. See Bring your own AI keys.
- Model status and Model migrations: which AI models you can use and proposals to replace retiring ones. See Model status and migrations.
The MCP server for AI assistants is under Automation → MCP. See Connect MCP clients to InfluenceBot.
Safety rules for machines
- An API key acts as the person who created it and can never do more than they can.
- Paid and publish calls follow your Automation Policy. When it needs a person, the call waits until someone confirms in the app. A machine never confirms its own call.
- Secrets (API keys and webhook signing secrets) are shown only once.
What can block you
- API keys, Webhooks, API docs and Zapier, Make & n8n appear only when the public API is enabled for your workspace. Otherwise the page says "Developer access is off for this workspace".
- Only owners and admins can manage API keys and webhooks.
- Screens marked MOCK are simulated: nothing is sent over the network.
Messages you may see
- "You need the Owner or Admin role"
- "API keys, webhooks and the API reference appear here once the public API is enabled for your workspace."
