Integration
Connect Bitbucket and Particle
When something happens in Bitbucket or Particle, 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 Particle 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 Particle can do together
From Bitbucket to Particle
When New pull request in Bitbucket
then Execute a logic function in Particle
When New pull request in Bitbucket
then Publish an event in Particle
From Particle to Bitbucket
When New device event (instant) in Particle
then Add branch in Bitbucket
When New device event (instant) in Particle
then Add pull request in 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 Particle
Triggers and actions 2 triggers · 14 actions
Trigger
New pull requestAction
Add branch/2.0/repositories/{workspace}/{repo_slug}/refs/branches
Action
Add pull request/2.0/repositories/{workspace}/{repo_slug}/pullrequests
Action
Add pull request comment/2.0/repositories/{workspace}/{repo_slug}/pullrequests/{id}/comments
Action
Add repository/2.0/repositories/{workspace}/{repo_slug}
Action
Get pull request/2.0/repositories/{workspace}/{repo_slug}/pullrequests/{id}
Action
List branches/2.0/repositories/{workspace}/{repo_slug}/refs/branches
Action
List pull requests/2.0/repositories/{workspace}/{repo_slug}/pullrequests
Action
List repositories/2.0/repositories/{workspace}
Action
Update pull request/2.0/repositories/{workspace}/{repo_slug}/pullrequests/{id}
Trigger
New device event (instant)Fires when a matching device event is published, delivered via a Particle webhook integration.
Action
Execute a logic functionRun a configured Particle Logic function and return its result.
Action
Get ledger instanceRetrieve the current data for a ledger instance (shared cloud/device key-value state).
Action
List devicesList all devices in your account or product fleet.
Action
Publish an eventPublish a custom event to the device cloud so other devices or integrations can subscribe to it.
Action
Set ledger instance dataUpdate the data stored in a ledger instance.
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 Particle
HubSpot to ParticleHubSpot is your all-in-one stop for all of your marketing software needs.
Gmail to ParticleGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ParticleGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to ParticleGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to ParticleMailchimp marketing automation and email platform.
ActiveCampaign to ParticleActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
Bitbucket and Particle, 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 Particle when something happens in Bitbucket?
Any of Particle's 5 actions, including Execute a logic function, Get ledger instance, List devices and Publish an event. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Particle to Bitbucket?
Yes. When something happens in Particle, your agent can act in Bitbucket too. This page covers both directions: Particle's triggers and Bitbucket's actions are listed here as well.
Do I have to build a connector for Bitbucket or Particle?
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.