Integration
Connect Diagrams.so and QuickBase
When something happens in Diagrams.so or QuickBase, your agent does the next thing in the other. Describe it and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Diagrams.so and QuickBase to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Diagrams.so and QuickBase can do together
From Diagrams.so to QuickBase
When New diagram in Diagrams.so
then Add app in QuickBase
When New diagram in Diagrams.so
then Add field in QuickBase
From QuickBase to Diagrams.so
When New or updated record in QuickBase
then Update diagram in Diagrams.so
When New record in QuickBase
then Edit diagram in Diagrams.so
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Diagrams.so and QuickBase
Triggers and actions 3 triggers · 35 actions
Trigger
New diagramFires when a new diagram is created in the account.
Action
Delete diagramDelete a diagram.
Action
Edit diagramEdit an existing diagram with a follow-up natural-language prompt.
Action
Export diagramExport a diagram as draw.io XML or SVG.
Action
Find gallery templatesSearch public community-shared architecture diagram templates in the gallery.
Action
Fix diagram warningApply an automated fix to a flagged Well-Architected warning on a diagram.
Action
Fork gallery templateFork a public gallery template into the account's own diagrams.
Action
Get diagramRetrieve a single diagram by id.
Action
Get diagram versionRetrieve a specific saved version of a diagram.
Action
Get diagram warningsRetrieve the Well-Architected findings and score for a diagram.
Action
Import diagramImport an existing draw.io file as a new diagram.
Action
List diagramsList the diagrams in the account.
Action
List diagram versionsList the saved versions of a diagram.
Action
Relayout diagramStart an automatic re-layout job on a diagram to clean up its arrangement.
Action
Update diagramUpdate a diagram's metadata (name, visibility, tags, etc).
Trigger
New or updated recordPolling trigger. Fires for each record added or modified in the specified Quickbase table, ordered by Date Modified. Records are deduped by their Record ID# (field 3).
Trigger
New recordPolling trigger. Fires for each new record added to the specified Quickbase table, ordered by Record ID#. Records are deduped by their Record ID# (field 3).
Action
Add appCreates a new Quickbase application in the connected realm, optionally with a description, app variables and security properties.
Action
Add fieldCreates a new field in a Quickbase table, optionally with display settings, type-specific properties and per-role permissions.
Action
Add tableCreate a new table in a QuickBase app.
Action
Delete appDelete a QuickBase app by id.
Action
Delete fieldDelete one or more QuickBase fields from a table.
Action
Delete recordsDelete records from a Quickbase table that match a query (Quickbase query language in the where clause).
Action
Delete tableDeletes a table from a Quickbase app, including all of the data within it.
Action
Get appGet the properties of a Quickbase application by its app ID.
Action
Get fieldGet a single QuickBase field by id.
Action
Get reportGet metadata for a single QuickBase report.
Action
Get tableGet the properties of a single Quickbase table by table ID and app ID.
Action
Get table fieldsList all fields (columns) for a Quickbase table, including field IDs, labels, and types.
Action
Get tables for appList all tables belonging to a Quickbase application.
Action
Insert or update recordsInsert new records or update existing ones in a Quickbase table. Pass data as an array of record objects keyed by field ID. Include the table's key field (or record ID field 3) to update; omit to insert.
Action
List reportsLists all reports defined on a Quickbase table.
Action
Query recordsQuery records from a Quickbase table. Optionally pass select (array of field IDs), where (Quickbase query language), sortBy, groupBy, and options (skip/top).
Action
Run formulaRuns a Quickbase formula against a table (and optionally a record) and returns the result as text.
Action
Run reportRun a Quickbase report by report ID and table ID and return its result rows.
Action
Update appUpdates an app's name, description, app variables and/or security properties. Properties left blank stay unchanged.
Action
Update fieldUpdates the properties and per-role permissions of an existing field in a Quickbase table. Properties left blank stay unchanged.
Action
Update tableUpdate an existing QuickBase table's properties.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Diagrams.so
Diagrams.so to PagerDutyPagerDuty is an incident management and on-call alerting platform.
Diagrams.so to DocuSealDocuSeal is an open-source platform for electronic document signing and management, offering secure, legally...
Diagrams.so to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Diagrams.so to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Diagrams.so to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Diagrams.so to Google SheetsGoogle Sheets
More into QuickBase
HubSpot to QuickBaseHubSpot is your all-in-one stop for all of your marketing software needs.
Pipedrive to QuickBasePipedrive is a sales CRM and pipeline management tool.
JIRA to QuickBaseAtlassian JIRA Cloud — issue tracking and project management.
Klaviyo to QuickBaseKlaviyo is a marketing automation platform for email and SMS.
JotForm to QuickBaseJotForm is a web-based WYSIWYG form builder. Create forms, integrate them into your site, and collect...
PandaDoc to QuickBasePandaDoc helps you build and deliver sales quotes and proposals and track presentations and close deals...
Questions
Diagrams.so and QuickBase, answered
What can start an automation from Diagrams.so?
Any of Diagrams.so's 1 trigger in the catalog, including New diagram. Describe the moment in plain language and your agent picks the right one.
What can your agent do in QuickBase when something happens in Diagrams.so?
Any of QuickBase's 21 actions, including Update app, Update field, Update table and Add app. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from QuickBase to Diagrams.so?
Yes. When something happens in QuickBase, your agent can act in Diagrams.so too. This page covers both directions: QuickBase's triggers and Diagrams.so's actions are listed here as well.
Do I have to build a connector for Diagrams.so or QuickBase?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.