Skip to main content

​
Mobile app (FAQ)

​
Does the automation use the same login as the app?

No. The mobile app (and web dashboard) use a normal user session. Automations use the Agent API with X-Agent-Id and X-Api-Key only. You do not put your personal password into n8n, Zapier, or MCP clients. Details on device security (biometric unlock, sign out) are in Profile & app settings.

​
Can I create API keys on the web?

Yes, when your role allows it. Workspace owners can generate workspace API keys from the web dashboard (for example Quickstart Integration or Workspace / Integrations), as well as from the mobile app. The same X-Agent-Id and X-Api-Key headers apply. See Credentials.

​
What API does the mobile app use?

The app talks to a private HTTP API (authenticated with your user session) to load agents, approvals, team settings, and to register push tokens. Automations should use the documented Agent API (/v1/*) or MCP tools that proxy to the same backend—not the app’s internal endpoints.

​
Push notifications and opening an approval

If you allow notifications for the app (see system settings in Profile & app settings) and you are a subscriber for an agent, you may get a push when a new approval is created. Tapping the notification often opens the approval detail so you can respond immediately—see Agents & inbox.

​
Where is my “server URL”?

Your organization supplies the base URL for API calls (and the app may be preconfigured). Use that same host for POST /v1/approvals and related paths from Agent API.