> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nextlevelmca.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect from CRM workflows

> Give a CRM workflow's AI agent the NextLevel MCA tools with a workspace API key.

A CRM workflow can use NextLevel MCA's tools from its AI agent action. It can look up a deal, check which lenders fit, request documents or log a note, all while the workflow runs. Nobody is signed in while a workflow runs, so it connects with a workspace **API key**, not the sign-in that Claude and ChatGPT use.

<Note>
  The CRM's Ask AI assistant connects the same way as Claude. Follow the [Claude guide](/developers/mcp/connect-from-claude) for that. This page covers workflows only.
</Note>

## 1. Create a key for the workflow

<Steps>
  <Step title="Open Settings → Developers → API keys">
    Create a key and name it after the workflow, for example `Workflow: missing docs follow-up`. That name appears in the activity log on everything the workflow changes.
  </Step>

  <Step title="Give it only what the workflow needs">
    Pick a role and tick only the scopes the workflow's tools need. A workflow that only reads needs only the `:read` scopes. One that chases documents also needs `documents:write` and `portal:send`. See [roles and scopes](/developers/authentication#scopes-what-a-connection-may-touch).
  </Step>

  <Step title="Copy the key">
    It is shown once. It starts with `nlmca_live_`.
  </Step>
</Steps>

## 2. Add the connection in the workflow

In the workflow's AI agent action, add a tool and choose **Add MCP connection**. Fill it in like this:

| Field | Value |
| - | - |
| Connection name | `NextLevel MCA` |
| Server URL | `https://mcp.nextlevelmca.com` |
| Transport type | **HTTP Streamable** |
| Auth type | **Bearer Token** |
| Token | the key from step 1 |

Save, and the agent sees the NextLevel MCA tools. Describe the job in the action's prompt the way you would ask a colleague. The [example prompts](/developers/mcp/overview#what-you-can-ask) work here too.

<Warning>
  Tools such as `submit_deal`, `request_documents` and `send_merchant_portal` send real email and text messages, and a workflow runs them without asking first. Test on one contact before you publish the workflow, and leave off the scopes the workflow should not use.
</Warning>

## What the workflow can do

The key decides everything:

* **Workspace.** It works only in the workspace that created it.
* **Role and scopes.** It can do only what its role and scopes allow. A tool that needs a scope the key lacks returns a message naming that scope, and nothing else happens.
* **Activity log.** Changes are recorded under the key's name, not a person's.

## Revoke access

Revoke the key under **Settings → Developers → API keys**. The workflow's next call is refused. Deleting the connection in the CRM does not revoke the key, so do both when you retire a workflow.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.