OpenParable
Skip to content
← Back to skills

Dinobase

Apps & Automation
dinobase

Dinobase is an Agent Skill for apps & automation published in the DinobaseHQ/dinobase repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Set up and query business data across 100+ sources (Stripe, HubSpot, Salesforce, etc.) via SQL. Agent-driven setup, cross-source joins, mutations.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/DinobaseHQ/dinobase/blob/HEAD/integrations/openclaw/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/dinobase, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Dinobase

Dinobase is an agent-first database. It syncs data from 100+ SaaS APIs, databases, and files into a SQL database (DuckDB). You query across all sources with standard SQL.

When to use

  • Setting up data connections for a user (first time or adding new sources)
  • Answering questions that span multiple business tools (CRM + billing + support)
  • Querying synced business data via SQL (Stripe, HubSpot, Salesforce, GitHub, etc.)
  • Cross-source joins and aggregations (e.g., customers with overdue invoices AND open tickets)
  • Writing data back to sources (UPDATE/INSERT with preview + confirm)

When NOT to use

  • Real-time API calls to a single service (use the service's API directly)
  • File system operations or general shell tasks
  • Data that hasn't been added to Dinobase yet (check with dinobase status first)

Setup (agent-driven)

You can fully set up Dinobase for the user. It runs entirely locally — no account required.

Step 1: Check existing state

dinobase status

This shows any sources that are already configured. If Dinobase isn't initialized yet, proceed with setup below.

Step 2: Set up locally

dinobase init

This initializes a local Dinobase database. Everything works locally — connecting sources, syncing, and querying.

Step 3: Discover what the user needs

Ask the user what tools and data sources they use. Then check what's available:

dinobase sources --available

This returns JSON with full metadata per source:

[
  {
    "name": "stripe",
    "description": "Stripe payments (customers, subscriptions, charges, invoices)",
    "supports_oauth": false,
    "credential_help": "Stripe Dashboard > Developers > API keys (use the Secret key)",
    "credentials": [{"name": "stripe_secret_key", "cli_flag": "--api-key", ...}]
  },
  {
    "name": "hubspot",
    "description": "HubSpot CRM (contacts, companies, deals, tickets)",
    "supports_oauth": true,
    "credential_help": "HubSpot > Settings > Integrations > Private Apps > create app > copy token",
    "credentials": [{"name": "api_key", "cli_flag": "--api-key", ...}]
  }
]

Step 4: Connect sources

For each source the user wants, connect it with an API key:

  1. Check credential_help from the sources list
  2. Tell the user where to find the key
  3. Run:
dinobase add <source_type> --<cli_flag> <value>

Example:

dinobase add stripe --api-key sk_live_...

Step 5: Sync data

dinobase sync

This runs the sync directly. Check status:

dinobase status

Step 6: Verify

dinobase info

Confirm that sources appear with non-zero table and row counts.

Workflow (querying data)

Always follow this sequence when answering data questions:

  1. Run dinobase info to see what sources and tables exist
  2. Run dinobase describe <schema>.<table> on relevant tables to see columns, types, and sample data
  3. Write SQL and run it with dinobase query "<sql>"
  4. If the query returns a mutation preview, ask the user before running dinobase confirm <mutation_id>

Commands

All commands output JSON by default (machine-readable). Add --pretty for human-readable output.

Connect sources

dinobase sources --available                # list all 100+ source types with auth info
dinobase add stripe --api-key sk_test_...   # API key connect

Discover data

dinobase info                       # overview of all sources, tables, freshness
dinobase status                     # source status with freshness indicators
dinobase describe stripe.customers  # table schema: columns, types, sample rows

Query data

# Run SQL (DuckDB dialect). Tables are schema.table
dinobase query "SELECT c.email, s.status FROM stripe.customers c JOIN stripe.subscriptions s ON c.id = s.customer_id WHERE s.status = 'past_due'"

# Limit rows returned (default 200, max 10000)
dinobase query "SELECT * FROM hubspot.contacts" --max-rows 500

Cross-source queries

Join across sources using shared columns (email, company name, IDs):

dinobase query "
SELECT c.email, c.name, i.amount_due, t.subject as ticket_subject
FROM stripe.customers c
JOIN stripe.invoices i ON c.id = i.customer_id
JOIN zendesk.tickets t ON c.email = t.requester_email
WHERE i.status = 'past_due' AND t.status = 'open'
"

Mutations (write-back)

UPDATE and INSERT queries return a preview first. Nothing executes until confirmed.

# Step 1: Query returns preview with mutation_id
dinobase query "UPDATE hubspot.contacts SET lifecycle_stage = 'customer' WHERE email = '[email protected]'"

# Step 2: Confirm to execute (writes back to API + updates data)
dinobase confirm <mutation_id>

# Or cancel
dinobase cancel <mutation_id>

Keep data fresh

dinobase refresh stripe      # re-sync a specific source
dinobase refresh --stale     # re-sync only stale sources
dinobase sync                # sync all sources

Tips

  • Tables are always referenced as schema.table (e.g., stripe.customers, hubspot.contacts)
  • Use describe before writing queries to find correct column names and types
  • DuckDB SQL dialect: supports ILIKE, LIST, STRUCT, regexp_matches(), date functions
  • JSON output is default; only use --pretty when showing results directly to the user
  • If data seems stale, check dinobase status for freshness info and run dinobase refresh <source>
  • Cross-source joins work via shared columns — use describe on both tables to find join keys
  • For new users: start with dinobase init and API key auth