Integration
Connect Diagrams.so to Atlas AI Revenue Engine
When something happens in Diagrams.so, your agent does the next thing in Atlas AI Revenue Engine. 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 Atlas AI Revenue Engine 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 can start in Atlas AI Revenue Engine
When New diagram in Diagrams.so
then Add agent in Atlas AI Revenue Engine
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 Atlas AI Revenue Engine
Triggers and actions 1 trigger · 31 actions
- New diagram
Fires when a new diagram is created in the account.
- Delete diagram
Delete a diagram.
- Edit diagram
Edit an existing diagram with a follow-up natural-language prompt.
- Export diagram
Export a diagram as draw.io XML or SVG.
- Find gallery templates
Search public community-shared architecture diagram templates in the gallery.
- Fix diagram warning
Apply an automated fix to a flagged Well-Architected warning on a diagram.
- Fork gallery template
Fork a public gallery template into the account's own diagrams.
- Get diagram
Retrieve a single diagram by id.
- Get diagram version
Retrieve a specific saved version of a diagram.
- Get diagram warnings
Retrieve the Well-Architected findings and score for a diagram.
- Import diagram
Import an existing draw.io file as a new diagram.
- List diagrams
List the diagrams in the account.
- List diagram versions
List the saved versions of a diagram.
- Relayout diagram
Start an automatic re-layout job on a diagram to clean up its arrangement.
- Update diagram
Update a diagram's metadata (name, visibility, tags, etc).
- Add agent
Create a new AI agent from a template for a campaign.
- Add campaign
Create a new outbound/inbound calling campaign.
- Add contact
Manually add a contact to a campaign's contact list.
- Add tool
Create a new AI agent tool.
- Delete campaign
Delete a campaign.
- Delete contact
Delete a contact.
- Delete knowledge file
Delete a knowledge base file.
- Delete tool
Delete an AI agent tool.
- Get agent
Retrieve an AI agent by ID.
- Get campaign
Retrieve a campaign by ID.
- List campaigns
List all campaigns.
- List contacts
List contacts for a campaign.
- List knowledge files
List uploaded knowledge base files.
- List tools
List all AI agent tools.
- Update campaign
Update a campaign's settings.
- Update contact
Update a contact's details.
- Update tool
Update an AI agent tool's configuration.
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 Atlas AI Revenue Engine
Gmail to Atlas AI Revenue EngineGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Atlas AI Revenue EngineGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Diagrams.so and Atlas AI Revenue Engine, 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 Atlas AI Revenue Engine when something happens in Diagrams.so?
Any of Atlas AI Revenue Engine's 17 actions, including Update campaign, Update contact, Update tool and Add agent. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Atlas AI Revenue Engine to Diagrams.so?
Atlas AI Revenue Engine has no triggers in the catalog today, so automations start in Diagrams.so. If you need the other direction, ask: your agent reads Atlas AI Revenue Engine's API documentation and adds it.
Do I have to build a connector for Diagrams.so or Atlas AI Revenue Engine?
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.