Using NOCA with AI assistants
Connect NOCA to your AI assistant to build web apps, automations (flows) and AI bots connected to your business systems (Salesforce, HubSpot, Google, Slack and 100+ more), and to look up live records, all from a conversation.
NOCA works with any AI assistant that supports remote MCP servers with sign-in (OAuth), such as Claude, ChatGPT, Microsoft Copilot and Grok.
What you need
A NOCA account.
Sign up at app.noca.ai.
An AI assistant plan that lets you add custom connectors (sometimes called MCP servers, apps or integrations).
The systems you want to use (Salesforce, Slack, and so on) connected in NOCA.
You can also connect them from the conversation when a request needs one; see Connecting a system.
Set up
Turn on MCP in NOCA
1- In NOCA, open Settings → MCP (app.noca.ai/account/settings/mcp) and turn on Enabled.
Do this once for each NOCA account you want to use from an AI assistant.
Add NOCA to your AI assistant
1- In your AI assistant’s settings, add a custom connector (MCP server).
2- Name it NOCA and enter the URL https://app.noca.ai/mcp.
3- Connect, sign in to NOCA, and choose the account and environment to connect.
On business plans, an administrator may need to add or allow the connector for the organization first.
To use a different account, disconnect NOCA in your AI assistant and connect again. You can also choose a different environment by connecting with that environment’s own URL.
Check it works
Ask: “List my NOCA flows.” You should see your flows from NOCA.
What you can do
| Area | Examples |
| Apps | Build forms, portals and sites from a description. Change an existing app, preview it on desktop, tablet and mobile, test its forms, and publish it. |
| Flows | Design automations step by step, triggered manually, by an API call, or by an event in a connected system (a new Salesforce record, a Slack message). Validate, test, publish and run them, and see what each run did. |
| Bots | Create chat bots that answer from your files, web pages and instructions, add automations to them, chat with them to test, and publish. |
| Documents | Fill Word templates and PDF forms from your data, generate PDF documents, and collect signatures. |
| Data | Look up live records in connected systems, for example “the last 5 Salesforce opportunities over $50k”. |
| Your own flows as tools | Share published flows so your AI assistant can run them directly, each under its own name. |
In Claude, AI image, video and voice generation and actions that move money (payments, payouts, transfers) are not available. Existing flows that use them keep running in NOCA.
Example requests
“Build a customer intake form that creates a Salesforce lead and posts to #sales in Slack.”
“When a HubSpot deal moves to Closed Won, create an onboarding task in Asana and email the customer.”
“Show me the last 5 runs of my invoice flow and why the latest one failed.”
“Create a support bot that answers from our help-center docs.”
“Turn this Word contract into a template that fills from the Salesforce opportunity.”
In AI assistants that support interactive cards, NOCA shows progress while it builds an app or bot. Every result includes links to open it in NOCA.
Permissions
You decide what AI assistants can do in your account. In Settings → MCP, select the gear icon next to Enabled:
| Setting | What it allows | Default |
| Builder and App tools | Create and edit apps, flows and bots; manage connections; test forms and flows | On |
| Data read | Read flow runs, logs and records in connected systems; chat with bots | On |
| Data write | Run flows, which can create, update or delete data in your connected systems | Off |
| Admin tools | Publish, unpublish and restore versions; delete apps, flows and bots | On |
These settings apply to everyone in the account, whichever AI assistant they use. After changing them, disconnect and reconnect NOCA in your AI assistant so it picks up the new set of tools.
Sharing flows
Under Available Flows on the same page, choose which published flows AI assistants can run as tools. Running them also needs Data write.
Safety
Every NOCA action is labelled as reading or changing data, so AI assistants that support it ask you before running changes.
Deleting, unpublishing or restoring an app, flow or bot needs your confirmation first, on a card or in the conversation. Nothing is removed until you confirm.
Restoring a version changes the draft only; the live version stays until you publish.
Credentials for your systems are entered on NOCA’s own setup page, never in the conversation.
Connecting a system from the conversation
If a request needs a system that isn’t connected yet, NOCA gives you a Connect [system] card, or a link in AI assistants without cards.
Select Connect (or open the link). NOCA’s setup page opens in a pop-up window or a new tab.
Sign in to the same NOCA account, then sign in to the system and save the connection.
Go back to the conversation. Where cards are supported, the card notices the new connection on its own and shows Continue building; otherwise, tell the assistant you’re done.
Setup requests expire after one hour. Cancel stops the request without touching connections you already have.
Billing
Record lookups (reading records from a connected system) are charged at your account’s Schema Usage rate, set by NOCA. One lookup can include up to 10 queries and is charged once.
Everything else is free through MCP: building, editing, testing, publishing, deleting, running flows, and reading runs and logs.
A lookup is not charged if every query in it fails, or if it’s cancelled or interrupted.
Each charged lookup appears in Logs → Integration Logs.
Troubleshooting
| Problem | What to do |
| Signing in to NOCA fails | Check the URL is https://app.noca.ai/mcp and that Enabled is on in Settings → MCP for the account you chose, then reconnect. |
| The wrong account’s data shows up | Disconnect NOCA in your AI assistant, connect again, and choose the right account and environment, or connect with the right environment’s URL. |
| A tool or action is missing | Turn on the matching setting in Permissions, then disconnect and reconnect NOCA. |
| “Run” or “publish” is refused | Running flows needs Data write; publishing and deleting need Admin tools. |
| The connection pop-up doesn’t open | Allow pop-ups for your AI assistant’s site, or use Open in browser on the card. |
| The connection stays on “pending” | Make sure you saved and tested the connection in NOCA, then return to the conversation. Requests expire after one hour; ask for a new one. |
| A flow run failed | Ask “why did the last run of [flow] fail?” NOCA returns the run step by step. You can also open Logs → Integration Logs in NOCA. |
| An app build is taking a while | Builds usually take a few minutes. Ask for the build status, or watch the card where cards are supported. |
Still stuck? Email support@noca.ai.
Privacy
Your AI assistant sends NOCA only what each action needs, such as the app description, flow settings, or the files you choose to upload. See the NOCA privacy policy for how this data is used and stored.