Integration
Connect Siteleaf to Workato Api Proxy
When New Collection fires in Siteleaf, your agent runs Update recipe in Workato Api Proxy. Describe the whole flow 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 Siteleaf and Workato Api Proxy 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 Workato Api Proxy
When New Collection in Siteleaf
then Update recipe in Workato Api Proxy
When New Document in Siteleaf
then Start recipe in Workato Api Proxy
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 Workato Api Proxy
Triggers and actions 4 triggers · 22 actions
Trigger
New CollectionTriggered when a new collection is created.
Trigger
New DocumentTriggered when a new document is created.
Trigger
New PageTriggered when a new page is created.
Trigger
New SiteTriggered when a new site is created.
Action
Add CollectionCreate a new collection on a site.
Action
Create DocumentCreates a new document.
Action
Create PageCreates a new page.
Action
Delete CollectionDelete a collection.
Action
Delete DocumentDelete a document.
Action
Delete PageDelete a page.
Action
Get DocumentGet a single document by id.
Action
Get PageGet a single page by id.
Action
Get SiteGet a single site by id.
Action
List CollectionsList collections for a site.
Action
List DocumentsList documents in a collection, filterable by search/visibility/extensions.
Action
List PagesList pages for a site, filterable by search/visibility/extensions.
Action
List SitesList all sites for the authenticated user.
Action
Update CollectionUpdate a collection's title/path/metadata.
Action
Update DocumentUpdate an existing document's title/body/tags/categories/metadata.
Action
Update PageUpdate an existing page's title/body/metadata.
Action
Update SiteUpdate a site's settings.
Action
Get jobReturns one job run of a recipe, including its status, timing, error details and the input and output of each step.
Action
Get recipeReturns the details of a Workato recipe, including its name, status, connections and step definitions.
Action
List jobsReturns the jobs run by a recipe, up to 1,000 at a time, along with succeeded and failed job counts.
Action
Start recipeStarts a stopped Workato recipe so it begins processing trigger events.
Action
Update recipeUpdates an existing stopped recipe's name, steps, connections, folder or description. Running recipes cannot be updated.
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 KmalServico Gold Price DatasetLive gold price per gram across 188 countries at six purities, converted from spot price and FX rates
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...
More into Workato Api Proxy
HubSpot to Workato Api ProxyHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Workato Api ProxySalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Workato Api ProxySlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Workato Api ProxyGoogle Sheets
Gmail to Workato Api ProxyGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Workato Api ProxyGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Siteleaf and Workato Api Proxy, 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 Workato Api Proxy when something happens in Siteleaf?
Any of Workato Api Proxy's 5 actions, including Update recipe, Get job, Get recipe and List jobs. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Workato Api Proxy to Siteleaf?
Workato Api Proxy has no triggers in the catalog today, so automations start in Siteleaf. If you need the other direction, ask: your agent reads Workato Api Proxy's API documentation and adds it.
Do I have to build a connector for Siteleaf or Workato Api Proxy?
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.