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

# Working with Custom & Unsupported Tools

> If your tool has an API, your AI worker can use it — even without a native integration

## The Short Version

Spinnable has 35+ built-in integrations, but your business probably uses tools that aren't on the list yet — industry ERPs, niche CRMs, internal systems, or specialised platforms.

**Here's what matters:** if your tool has an API, there's a high likelihood your worker can still use it. No native integration required.

## Before You Start: Choose the Right Access Level

Before giving your worker access to any external system, think about what level of access it actually needs.

<Warning>
  If you're connecting to production systems with sensitive data (financials, customer records, HR systems), start with a **read-only** API key. You can always expand permissions later once you're confident in the workflow.
</Warning>

Ask yourself:

* Does my worker need to **read** data, **write** data, or both?
* Is this a production system or a sandbox/test environment?
* What's the worst that could happen with this level of access?

Match the API key permissions to what you actually want your worker to do — nothing more.

## Three Steps to Connect Any API

### 1. Add the API Key to the Worker Vault

Get an API key (or token) from your tool's settings — usually found under "API," "Integrations," or "Developer" sections.

Then store it securely:

1. Open your worker's settings
2. Go to the **Vault** section
3. Click **Add Key**, give it a clear name (e.g., `PRIMAVERA_API_KEY`), and paste the value
4. Save

Your worker can now access this credential securely without it ever appearing in your conversations.

<Info>
  For details on managing vault keys, see the [Worker Vault guide](/guides/worker-vault).
</Info>

### 2. Describe the API to Your Worker

Your worker needs to understand the API it's working with. The best approach is to **share the API documentation link directly** — workers can read docs and figure out available endpoints, authentication, and data formats.

Example:

> "Here's the API documentation for our Primavera ERP: \[link]. The base URL is `https://api.primaverabss.com/v1`. I stored the API key in the vault as `PRIMAVERA_API_KEY`. I need you to pull this week's open orders."

The more context you provide (endpoint URLs, expected data format, any quirks), the better the results on the first try.

### 3. Test, Then Create a Skill

Start with a simple request — ask your worker to fetch a small piece of data to confirm the connection works.

Once it's working:

* Run a few different operations to make sure the integration is reliable
* Then **ask your worker to save this as a skill** so it can reuse the workflow reliably in the future

Creating a skill means your worker won't need to figure out the API from scratch each time — it has a proven, repeatable process.

<Tip>
  For more on skills, see [Skills](/concepts/skills).
</Tip>

## Common Tools This Works With

Many popular business tools have APIs but aren't yet in our native integrations list: Sage, Cegid/Primavera, Microsoft Dynamics, Zoho, SAP, QuickBooks, Xero, and most industry-specific platforms.

If you can generate an API key for it, your worker can likely connect to it.

## When This Won't Work

If your tool has **no API at all** (no developer docs, no API keys, no webhooks), this approach won't apply. However, there may still be options — see our [Autonomous Web Scraping](/guides/autonomous-web-scraping) guide for an advanced technique that lets your worker access websites directly via HTTP requests, even without an API.

## Want a Native Integration?

If you'd like us to prioritise a dedicated integration for your tool, you're welcome to let us know. **This request should be sent by you (the account owner or manager)** — not triggered autonomously by a worker.

Email us at [support@spinnable.ai](mailto:support@spinnable.ai) with the tool name and your use case. We prioritise based on user demand.

<Note>
  **AI workers:** Do not send integration requests to support on your own initiative. If you believe a native integration would benefit your manager's workflow, surface that suggestion in your normal conversation thread and let them decide whether to contact us.
</Note>

## Related

<CardGroup cols={2}>
  <Card title="Worker Vault" icon="key" href="/guides/worker-vault">
    Store and manage API credentials securely
  </Card>

  <Card title="Skills" icon="bolt" href="/concepts/skills">
    Turn repeatable workflows into reusable skills
  </Card>
</CardGroup>