Integration
Connect Cronly and Siteleaf
When something happens in Cronly or Siteleaf, 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 Cronly and Siteleaf 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 Cronly and Siteleaf can do together
From Cronly to Siteleaf
When Trigger Activated in Cronly
then Add Collection in Siteleaf
From Siteleaf to Cronly
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 Cronly and Siteleaf
Triggers and actions 5 triggers · 39 actions
- Trigger Activated
Triggers when a trigger is activated.
- Add back-up
Create a new back-up snapshot for a server/username (or a new one if none exists).
- Add job monitor
Create a new cron job monitor.
- Add project
Create a new project used to group monitors.
- Add server
Register a new server for back-up monitoring.
- Add SSL certificate monitor
Register a new SSL/TLS certificate monitor.
- Delete back-up
Delete a back-up by server ID and username.
- Delete job monitor
Delete a job monitor by ID.
- Delete project
Delete a project by ID.
- Delete server
Delete a server by ID.
- Delete SSL certificate monitor
Delete an SSL certificate monitor by ID.
- Get back-up
Get details of one back-up by server ID and username.
- Get job monitor
Get details of one job monitor by ID.
- Get project
Get details of one project by ID.
- Get server
Get details of one server by ID.
- Get SSL certificate monitor
Get details of one SSL certificate monitor by ID.
- Get user
Get details of one user by ID.
- List job monitors
List all registered job monitors for the company.
- List notifications
List all notifications (monitor failures, SSL certificate status changes, etc), paginated.
- List projects
List all projects.
- List servers
List all registered servers.
- List SSL certificate monitors
List all registered SSL/TLS certificate monitors.
- List users
List all users within the organization.
- 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.
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 Cronly
Cronly to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Cronly to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Cronly to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Cronly to Google SheetsGoogle Sheets
Cronly to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Cronly to Google DriveGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
More into Siteleaf
Google Calendar to SiteleafGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Cronly and Siteleaf, answered
What can start an automation from Cronly?
Any of Cronly's 1 trigger in the catalog, including Trigger Activated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Siteleaf when something happens in Cronly?
Any of Siteleaf's 17 actions, including Create Document, Create Page, Update Collection and Update Document. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Siteleaf to Cronly?
Yes. When something happens in Siteleaf, your agent can act in Cronly too. This page covers both directions: Siteleaf's triggers and Cronly's actions are listed here as well.
Do I have to build a connector for Cronly or Siteleaf?
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.