Skip to main content

​
Overview

Tools enable AI workers to perform actions and access external systems. Spinnable provides a comprehensive tool ecosystem with granular permission controls to ensure security while maximizing functionality.

​
Key Concepts

​
Worker-Level Configuration

Each worker can have a different set of tools. Connections to app accounts belong to the workspace, with attribution to the person who connected them. See Workspaces.

​
Two-Step Access Model

  1. Open Settings > Tools for the selected workspace and connect the app account you intend to use.
  2. Open the worker’s Tools, add the tool, and select the right connection for that worker. A connection alone does not give every worker access.
Use separate accounts and least-privilege capabilities when appropriate. Tool Permissions explains read versus send access.

​
Available Tool Categories

For a complete list of all available tools and detailed documentation, see our Tools & Integrations directory.

​
Communication Tools

  • Email: Send and receive emails through integrated accounts
Note: Slack is configured as a communication channel by inviting your worker directly to your Slack workspace, rather than as a tool in Settings > Tools. See the Communication Channels guide.

​
Development Tools

  • GitHub: Manage repositories, issues, pull requests, and code reviews
  • GitLab: Version control and CI/CD pipeline management
  • Jira: Issue tracking and project management

​
Productivity Tools

  • Google Workspace: Access Gmail, Calendar, Drive, Docs, and Sheets
  • Microsoft 365: Outlook, Calendar, OneDrive integration
  • Notion: Database queries and page management

​
Data & Analytics

  • SQL Databases: Execute queries on connected databases
  • APIs: Custom API integrations with authentication

​
Knowledge Tools

  • Web Search: Real-time internet search capabilities
  • Knowledge Base: Access to your team’s documentation

​
Configuring Tools for a Worker

1

Connect the service

Switch to the worker’s workspace. In Settings > Tools, connect the app account and complete authorization. Verify that the connection is available.
2

Grant worker access

Open Workers, select the worker, then open its Tools. Add the needed capability and select the intended connection. For example, Gmail (read) does not give permission to send; add Gmail (send) separately if needed.
3

Run a small test

Ask the worker to perform a limited task, confirm which account it used, and adjust access if necessary.

​
Best Practices

Grant only the minimum permissions necessary for a worker to perform its intended function. Start with read-only access and expand as needed.
Review worker tool permissions quarterly to ensure they align with current responsibilities. Remove unused tools to reduce security surface.
Create specialized workers for distinct tasks rather than one worker with all permissions. For example:
  • Support Worker: Zendesk (read/write) + Slack communication channel
  • Code Review Worker: GitHub (read + comment)
  • Deployment Worker: GitHub + AWS (write)
Use the Activity Log to track which tools workers are using and identify unusual patterns.
Create a duplicate worker in a development environment to test tool configurations before deploying to production.

​
Common Tool Workflows

​
Automating GitHub Issue Triage

  1. Tools Needed: GitHub (read issues, write labels, write comments)
  2. Configuration: Enable GitHub tool with write permissions for labels and comments
  3. Worker Behavior: Monitors new issues, categorizes them, adds appropriate labels, and posts initial responses

​
Customer Support Automation

  1. Tools Needed: Zendesk (read/write tickets), Knowledge Base (read) (plus Slack as a communication channel)
  2. Configuration: Connect tools with appropriate permissions
  3. Worker Behavior: Receives Slack questions, searches knowledge base, creates Zendesk tickets for complex issues

​
Documentation Sync

  1. Tools Needed: GitHub (read code/comments), Notion (write pages) (plus Slack as a communication channel)
  2. Configuration: GitHub read access, Notion write access, Slack channel posting
  3. Worker Behavior: Monitors code changes, updates documentation in Notion, notifies team via Slack

​
Security Considerations

​
API Key Management

  • Spinnable securely stores all API keys and credentials
  • Keys are encrypted at rest and in transit
  • Workers never see or expose raw credentials

​
Audit Logging

All tool actions are logged with:
  • Timestamp
  • Worker ID
  • Tool and method used
  • Success/failure status
  • User context (if applicable)

​
Rate Limiting

Configure rate limits per worker to prevent:
  • Accidental API quota exhaustion
  • Runaway automation loops
  • Service degradation

​
IP Whitelisting

For sensitive integrations, configure IP restrictions at the account level to ensure tools can only be accessed from approved networks.

​
Troubleshooting

  1. Confirm you’re in the worker’s workspace and find the intended account under Settings > Tools. A connection in another workspace is not enough.
  2. Open the worker’s Tools and check that the needed capability is added and uses the intended connection. For example, Gmail read access does not enable Gmail send; add the send capability if the task requires it.
  3. Retry with a small task. If the account or capability is still missing, ask a manager of that worker to check its tool access. See Tool Permissions.
Check the selected workspace’s app connection under Settings > Tools and retry authorization or reconnect it if that option is offered. Complete the provider’s authorization flow with an account permitted to use the app; if your organization restricts app consent, ask its administrator to approve the integration. Then recheck the connection selected in the worker’s Tools and run a small test. If it still fails, note the app, workspace and error message when you contact support (do not send credentials).
In Settings > Tools, verify which workspace connection you authorized. In the worker’s Tools, select the intended connection for the capability, then test a read-only task before permitting any write or send action. Avoid disconnecting a shared connection without checking other workers that use it.

Tool Permissions

Learn about tool permissions and access control

Tools Overview

See all available tools and integrations

Managing Workers

Configure workers and their tool access

API Reference

Full API documentation for tool integrations

​
Next Steps

1

Review Available Integrations

Check which apps are connected in the selected workspace
2

Plan Worker Roles

Map out which workers need which tools based on their responsibilities
3

Configure Tools

Enable and configure tools for each worker following the principle of least privilege
4

Test Thoroughly

Verify tool access and permissions before deploying to production
5

Monitor and Iterate

Use activity logs to optimize tool configurations over time