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

# ServiceNow REST fallback

> Call ServiceNow REST API endpoints that do not yet have a typed Flow module.

export const flowWebUrl = "https://app.letsflow.ai";

Flow runs ServiceNow REST fallback actions through the ServiceNow (API key) connection shared with the Table API module. ServiceNow REST fallback is an action module, not a separate connection in the catalogue. Admins choose which REST actions each team can use. This guide covers API key setup, not ServiceNow (OAuth).

<Tabs>
  <Tab title="API key connection">
    ### Prepare in ServiceNow (API key)

    In ServiceNow, create a REST API key with access only to the REST endpoints your automations need. Flow sends this key in the `x-sn-apikey` header. Have your HTTPS ServiceNow instance URL and API key ready.

    ### Connect in Flow

    <Steps>
      <Step title="Find the ServiceNow (API key) integration">
        1. Open **Integrations**.
        2. Choose **Add connection**.
        3. Search for **ServiceNow (API key)**.
        4. Select the **ServiceNow (API key)** card, not **ServiceNow (OAuth)**.

        <a className="flow-app-link" href={flowWebUrl}>
          Open Flow

          <svg aria-hidden="true" viewBox="0 0 24 24" width="14" height="14" fill="none" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round">
            <path d="M7 7h10v10" />

            <path d="M7 17 17 7" />
          </svg>
        </a>
      </Step>

      <Step title="Connect">
        1. In **Teams**, choose the team that will use the connection.
        2. Continue through **Permissions** to **Connect**.
        3. Enter your HTTPS ServiceNow instance URL without a path, query, or fragment.
        4. Complete the API key credential step when prompted.
        5. Open the new connection's **Automations** tab.
        6. Choose **Enable** for the intended team if Automations is not enabled.
        7. Select the ServiceNow REST fallback actions the team needs without deselecting Table API actions that are still in use. REST fallback actions are high risk and are off in the recommended selection.
        8. Choose **Save** if you changed the action selection. Adding REST fallback actions creates a custom selection.
      </Step>
    </Steps>
  </Tab>
</Tabs>

## Permissions and scopes

This integration does not define provider scopes.

## Supported actions

| Action | Description | <Tooltip tip="Risk estimates the impact of the action. Low reads provider data, medium changes existing records, and high can grant access, remove data, disable resources, or make broad changes.">Risk</Tooltip> |
| - | - | - |
| REST DELETE | Calls a relative ServiceNow /api/ DELETE endpoint through the connected instance. Use a typed API module when one is available. | <Badge color="red" size="sm" shape="pill">high</Badge> |
| REST GET | Calls a relative ServiceNow /api/ endpoint through the connected instance. Use a typed API module when one is available. | <Badge color="red" size="sm" shape="pill">high</Badge> |
| REST PATCH | Calls a relative ServiceNow /api/ PATCH endpoint through the connected instance. Use a typed API module when one is available. | <Badge color="red" size="sm" shape="pill">high</Badge> |
| REST POST | Calls a relative ServiceNow /api/ POST endpoint through the connected instance. Use a typed API module when one is available. | <Badge color="red" size="sm" shape="pill">high</Badge> |
| REST PUT | Calls a relative ServiceNow /api/ PUT endpoint through the connected instance. Use a typed API module when one is available. | <Badge color="red" size="sm" shape="pill">high</Badge> |


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