Skip to main content

​
Overview

Spinnable supports 35+ pre-built integrations, but your business might use tools that aren’t on the list yet — industry-specific ERPs, niche CRMs, internal APIs, or specialized services. Good news: If your tool has an API, your AI worker can likely still connect to it using the Worker Vault and code execution.
Pre-built integrations (like Gmail or Notion) offer the smoothest experience with OAuth sign-in and dedicated UI. The custom approach described here requires a bit more setup but opens the door to virtually any service with an API.

​
When to Use This Approach

ScenarioWhat to Use
Tool is in the supported listUse the native integration — it’s easier and more reliable
Tool has a REST API or SDKUse the Vault + code execution (this guide)
Tool has no API at allContact us at support@spinnable.ai — we may be able to help

​
Step 1: Check If Your Service Has an API

Most modern business software offers an API. Here’s how to find out:
  1. Search for “[Your Tool Name] API documentation” — most services publish their API docs publicly
  2. Check your tool’s settings — look for sections labeled “API,” “Integrations,” “Developer,” or “Webhooks”
  3. Look for API key generation — if you can create an API key or access token, the service has an API
Common tools with APIs that aren’t yet in our native integrations: Sage, Cegid/Primavera, Microsoft Dynamics, Zoho, SAP, QuickBooks, Xero, and many industry-specific platforms.

​
Step 2: Get Your API Credentials

Depending on the service, you’ll need one of:
  • API Key — A single string that authenticates your requests (most common)
  • API Key + Secret — A pair of credentials
  • Access Token — Often from an OAuth flow or developer portal
  • Username + Password — For basic authentication (less common in modern APIs)
Find these in your service’s developer settings, integrations page, or admin panel. If unsure, check the service’s API documentation for authentication instructions.
Never paste credentials directly into chat with your worker. Always use the Vault — it keeps your secrets encrypted and invisible in conversation history.

​
Step 3: Store Credentials in the Worker Vault

  1. Open your worker’s settings page
  2. Navigate to the Vault section
  3. Click Add Key
  4. Enter a descriptive key name (e.g., PRIMAVERA_API_KEY) and paste the secret value
  5. Click Save
Your worker will access this as an environment variable during code execution — for example, VAULT_PRIMAVERA_API_KEY. For full details on managing vault keys, see the Worker Vault guide.

​
Step 4: Ask Your Worker to Connect

Now simply tell your worker what you need. They’ll use code execution to call the API with your stored credentials. Example conversation:
You: “I need you to pull this week’s open orders from our Primavera ERP. The API base URL is https://api.primaverabss.com/v1 and the docs are at [link]. Use the API key I stored in the vault as PRIMAVERA_API_KEY.” Worker: “I’ll connect to your Primavera instance and pull the open orders. Let me make the API call…”
The more context you give your worker about the API (documentation links, endpoint URLs, expected data format), the better the results. Workers can read API documentation and figure out the right calls.

​
What Workers Can Do with Custom APIs

Once connected, your worker can:
  • Read data — Pull reports, look up records, fetch statistics
  • Create records — Add new entries, submit forms, create tickets
  • Update data — Modify existing records, change statuses
  • Automate workflows — Combine multiple API calls into a single task
  • Schedule recurring tasks — Set up regular data pulls or syncs

​
Limitations vs. Native Integrations

FeatureNative IntegrationCustom API (Vault)
Setup effortOne-click OAuthManual API key + instructions
Authentication refreshAutomaticMay need manual token rotation
Dedicated UI in Spinnable✓✗
Worker can use it✓✓ (via code execution)
Permission controlsGranular (read/write/delete)Depends on API key scope
ReliabilityManaged by SpinnableDepends on API stability

​
Tips for Best Results

Send your worker a link to the service’s API docs. They can read it and understand available endpoints, authentication methods, and data formats.
Test the connection by asking your worker to fetch a small piece of data first. Once that works, move on to more complex operations.
Name your keys clearly: DYNAMICS_CRM_API_KEY, SAGE_ACCESS_TOKEN, ERP_DB_PASSWORD. This makes it easy to manage multiple custom integrations.
If your API has rate limits (e.g., 100 requests per minute), let your worker know so they can pace their requests appropriately.

​
Need a Native Integration?

If you’d like us to build a dedicated integration for your tool, let us know at support@spinnable.ai. We prioritize based on user demand — the more requests we get for a tool, the sooner it gets built.

Worker Vault

Learn how to store and manage API credentials securely

Tools & Integrations

Browse all 35+ native integrations