Build solutions, not workarounds.
What do you want Siteleaf and Nango 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 Siteleaf can start in Nango
When New Collection in Siteleaf
then Add connection in Nango
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 Siteleaf and Nango
Triggers and actions 4 triggers · 28 actions
- New Collection
Triggered when a new collection is created.
- New Document
Triggered when a new document is created.
- New Page
Triggered when a new page is created.
- New Site
Triggered when a new site is created.
- Add Collection
Create a new collection on a site.
- Create Document
Creates a new document.
- Create Page
Creates a new page.
- Delete Collection
Delete a collection.
- Delete Document
Delete a document.
- Delete Page
Delete a page.
- Get Document
Get a single document by id.
- Get Page
Get a single page by id.
- Get Site
Get a single site by id.
- List Collections
List collections for a site.
- List Documents
List documents in a collection, filterable by search/visibility/extensions.
- List Pages
List pages for a site, filterable by search/visibility/extensions.
- List Sites
List all sites for the authenticated user.
- Update Collection
Update a collection's title/path/metadata.
- Update Document
Update an existing document's title/body/tags/categories/metadata.
- Update Page
Update an existing page's title/body/metadata.
- Update Site
Update a site's settings.
- Add connection
Imports (upserts) a connection into a Nango integration using credentials you already hold. If a connection with the same connection ID and integration already exists, its credentials are updated.
- Add connect session
Creates a short-lived (30 minute) Nango connect session and returns its token and connect link, which your end user can use to connect an integration through Nango Connect UI.
- Add integration
Creates a new integration in the Nango environment for a given provider.
- Delete connection
Deletes a Nango connection for the given integration.
- Delete integration
Deletes an integration from the Nango environment.
- Get connection
Returns a specific Nango connection, including its current credentials (Nango refreshes an expired access token before returning it).
- Get connect session
Get a Connect session by token.
- Get integration
Returns a specific Nango integration by its unique key.
- List integrations
Returns every integration configured in the connected Nango environment.
- Update connection
Edits a Nango connection's tags or its webhook URL override.
- Update integration
Edits an existing Nango integration: rename its ID, change its display name, toggle webhook forwarding, or replace its credentials or provider-specific configuration. Only the fields you fill in are changed.
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 Siteleaf
Siteleaf to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Siteleaf to StripeStripe is a payment processing platform for online businesses.
Siteleaf to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Siteleaf to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Siteleaf to TwilioCloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...
Siteleaf to TypeformBuild and publish online forms, surveys, and quizzes with Typeform.
More into Nango
HubSpot to NangoHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to NangoSalesforce is a leading enterprise customer relationship management (CRM) platform.
Google Sheets to NangoGoogle Sheets
Gmail to NangoGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to NangoGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Siteleaf and Nango, answered
What can start an automation from Siteleaf?
Any of Siteleaf's 4 triggers in the catalog, including New Collection, New Document, New Page and New Site. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Nango when something happens in Siteleaf?
Any of Nango's 11 actions, including Update connection, Update integration, Add connection and Add connect session. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Nango to Siteleaf?
Nango has no triggers in the catalog today, so automations start in Siteleaf. If you need the other direction, ask: your agent reads Nango's API documentation and adds it.
Do I have to build a connector for Siteleaf or Nango?
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.