Use Ninox from Claude
Add the Ninox connection to a Space that runs Claude, then use it from every channel in that Space.
Connect Ninox once, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.
Add the Ninox connection to a Space that runs Claude, then use it from every channel in that Space.
Add the Ninox connection to a Space that runs Codex, then use it from every channel in that Space.
Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.
Ninox lets teams build custom database apps without code, organizing data into teams, databases, tables, and records. In type.com, an operations team can ask Claude to list the teams or databases available, check details on a specific workspace, or delete a record that's no longer needed.
Connect Ninox once, then decide which Spaces can use it in threads, skills, automations, and coding work.
List every Ninox team available to the account, since each one holds its own set of databases, tables, and records.
List all the Ninox teams I have access to before I decide where to build this new app.
Pull the databases inside a specific Ninox team to confirm the right one exists before adding tables or records to it.
List the databases in our Ops team in Ninox so I can check if the inventory database already exists.
Delete a specific record from a table once its workspace, database, and table IDs are confirmed, clearing out stale entries.
Delete the duplicate customer record in our CRM table in Ninox after confirming the record ID with me.
Removes a record from a specified Ninox table, once the workspace, database, and table are confirmed.
Lists every database within a specific Ninox team, each containing its own tables and records.
Returns details for a single Ninox team by its ID, including the workspace name.
Lists every Ninox team the authenticated user has access to.
Ninox provides REST API access for low-code database applications. Integrations can connect custom databases, records, tables, files, and business workflows to external systems, using API access to synchronize data and automate operations across Ninox apps.
Yes. With a Ninox connection shared to a type.com Space, Claude can list teams and databases, check workspace details, or delete a specific record, all from a thread.
Ninox uses an API key, added once by an admin when the connection is created. Spaces building on Ninox apps can use it without seeing the key.
No. Deleting a record is permanent, so confirm the workspace, database, table, and record ID with your team before asking the agent to delete anything.
Not exactly. type.com uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.
Connect Contentful GraphQL to Claude in type.com to run persisted content queries and retrieve management tokens from a shared thread.
Connect Context7 MCP to Claude in type.com to resolve a library's ID and pull its current documentation into a shared thread.
Connect Convex to Claude in type.com to generate deploy keys, provision projects and deployments, and retire old ones as a team.
Connect Crowdin to Claude in type.com to add branches, files, and glossary terms to a localization project from a thread.