Integration
Connect Cronly to DocDroid
When Trigger Activated fires in Cronly, your agent runs Update Document in DocDroid. 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 Cronly and DocDroid 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 can start in DocDroid
When Trigger Activated in Cronly
then Update Document in DocDroid
When Trigger Activated in Cronly
then Upload Document in DocDroid
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 DocDroid
Triggers and actions 1 trigger · 27 actions
Trigger
Trigger ActivatedTriggers when a trigger is activated.
Action
Add back-upCreate a new back-up snapshot for a server/username (or a new one if none exists).
Action
Add job monitorCreate a new cron job monitor.
Action
Add projectCreate a new project used to group monitors.
Action
Add serverRegister a new server for back-up monitoring.
Action
Add SSL certificate monitorRegister a new SSL/TLS certificate monitor.
Action
Delete back-upDelete a back-up by server ID and username.
Action
Delete job monitorDelete a job monitor by ID.
Action
Delete projectDelete a project by ID.
Action
Delete serverDelete a server by ID.
Action
Delete SSL certificate monitorDelete an SSL certificate monitor by ID.
Action
Get back-upGet details of one back-up by server ID and username.
Action
Get job monitorGet details of one job monitor by ID.
Action
Get projectGet details of one project by ID.
Action
Get serverGet details of one server by ID.
Action
Get SSL certificate monitorGet details of one SSL certificate monitor by ID.
Action
Get userGet details of one user by ID.
Action
List job monitorsList all registered job monitors for the company.
Action
List notificationsList all notifications (monitor failures, SSL certificate status changes, etc), paginated.
Action
List projectsList all projects.
Action
List serversList all registered servers.
Action
List SSL certificate monitorsList all registered SSL/TLS certificate monitors.
Action
List usersList all users within the organization.
Action
Delete documentPermanently deletes a document from your DocDroid account.
Action
Find DocumentFinds documents in your DocDroid account whose name or file name matches the one you give.
Action
Get documentReturns a single DocDroid document with its settings, status and share links.
Action
Update DocumentUpdates the settings of an existing DocDroid document, such as its visibility, embedding, download and password options.
Action
Upload DocumentUploads a file to DocDroid as a new document, with optional visibility, embedding, download and password 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 crob.atPokémon team sharing and type chart data
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...
More into DocDroid
HubSpot to DocDroidHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to DocDroidSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to DocDroidSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to DocDroidGoogle Sheets
Gmail to DocDroidGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to DocDroidGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Cronly and DocDroid, 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 DocDroid when something happens in Cronly?
Any of DocDroid's 5 actions, including Update Document, Upload Document, Find Document and Get document. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from DocDroid to Cronly?
DocDroid has no triggers in the catalog today, so automations start in Cronly. If you need the other direction, ask: your agent reads DocDroid's API documentation and adds it.
Do I have to build a connector for Cronly or DocDroid?
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.