Integration
Connect Bitbucket and Cronly
When something happens in Bitbucket or Cronly, 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 Bitbucket and Cronly 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 Bitbucket and Cronly can do together
From Bitbucket to Cronly
When New pull request in Bitbucket
then Add back-up in Cronly
From Cronly to Bitbucket
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 Bitbucket and Cronly
Triggers and actions 2 triggers · 31 actions
- New pull request
- Add branch
/2.0/repositories/{workspace}/{repo_slug}/refs/branches
- Add pull request
/2.0/repositories/{workspace}/{repo_slug}/pullrequests
- Add pull request comment
/2.0/repositories/{workspace}/{repo_slug}/pullrequests/{id}/comments
- Add repository
/2.0/repositories/{workspace}/{repo_slug}
- Get pull request
/2.0/repositories/{workspace}/{repo_slug}/pullrequests/{id}
- List branches
/2.0/repositories/{workspace}/{repo_slug}/refs/branches
- List pull requests
/2.0/repositories/{workspace}/{repo_slug}/pullrequests
- List repositories
/2.0/repositories/{workspace}
- Update pull request
/2.0/repositories/{workspace}/{repo_slug}/pullrequests/{id}
- 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.
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 Bitbucket
Bitbucket to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Bitbucket to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Bitbucket to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Bitbucket to Google SheetsGoogle Sheets
Bitbucket to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Bitbucket to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Cronly
Mailchimp to CronlyMailchimp marketing automation and email platform.
ActiveCampaign to CronlyActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to CronlyOrganize anything with Airtable, a modern database created for everyone.
Asana to CronlyAsana is a collaborative information manager for workspace.
ClickUp to CronlyClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Questions
Bitbucket and Cronly, answered
What can start an automation from Bitbucket?
Any of Bitbucket's 1 trigger in the catalog, including New pull request. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Cronly when something happens in Bitbucket?
Any of Cronly's 22 actions, including Add back-up, Add job monitor, Add project and Add server. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Cronly to Bitbucket?
Yes. When something happens in Cronly, your agent can act in Bitbucket too. This page covers both directions: Cronly's triggers and Bitbucket's actions are listed here as well.
Do I have to build a connector for Bitbucket or Cronly?
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.