---
title: "Connect Buildkite to Clicksign - APIANT.ai"
description: "When \"New build\" fires in Buildkite, your agent runs \"Notifications Email\" in Clicksign."
canonical: "https://apiant.ai/connect/buildkite-to-clicksign"
---

# Connect Buildkite to Clicksign

When **New build** fires in [Buildkite](https://apiant.ai/connections/buildkite), your agent runs **Notifications Email** in [Clicksign](https://apiant.ai/connections/clicksign). Describe the whole flow and it is built, tested on every scenario and kept running.

Buildkite **2** triggers Buildkite **12** actions Clicksign **11** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want Buildkite and Clicksign to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any 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.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

### 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)](https://apiant.ai/docs/mcp)

Example flows

## What Buildkite can start in Clicksign

- When **New build** in Buildkite then **Notifications Email** in Clicksign
- When **Build finished** in Buildkite then **View Document** in Clicksign

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 Buildkite and Clicksign

## Triggers and actions 2 triggers · 23 actions

- Trigger

**Build finished**

Triggers when a Buildkite build finishes (passed, failed, canceled or otherwise completed).

- Trigger

**New build**

Triggers when a new build is scheduled in a Buildkite pipeline.

- Action

**Add annotation**

Creates an annotation (a Markdown or HTML note) on a Buildkite build, optionally appending to an existing annotation with the same context.

- Action

**Add build**

Creates (triggers) a new build on a Buildkite pipeline for a given commit and branch, and returns the new build.

- Action

**Add pipeline**

Creates a new pipeline in a Buildkite organization from a repository and YAML steps configuration.

- Action

**Cancel build**

Cancels a running or scheduled build in a Buildkite pipeline and returns the updated build.

- Action

**Delete pipeline**

Permanently deletes a pipeline from your Buildkite organization.

- Action

**Get build**

Returns a single build of a Buildkite pipeline by its build number, including its state, commit, jobs and pipeline details.

- Action

**Get pipeline**

Returns a Buildkite pipeline's full details, including its repository, default branch, steps and build counts.

- Action

**List agents**

Returns the connected and stopping agents in a Buildkite organization, optionally filtered by name, hostname, version or queue.

- Action

**List builds**

Returns the builds of a Buildkite pipeline, newest first, optionally filtered by branch, commit, state, creator or date range.

- Action

**List pipelines**

Returns the pipelines in a Buildkite organization, optionally filtered by pipeline name or repository URL.

- Action

**Rebuild build**

Starts a new build that re-runs an existing build of a pipeline, and returns the new build.

- Action

**Update pipeline**

Updates one or more settings of an existing Buildkite pipeline, such as its name, repository, YAML steps or branch filters.

- Action

**Create Signer**

Creates a signer on a Clicksign envelope and returns the new signer record, ready to be linked to the envelope's documents.

- Action

**Delete Document**

Deletes a draft document from a Clicksign envelope.

- Action

**Delete Signer**

Deletes a signer from an envelope, as long as the signer has not started signing.

- Action

**List Documents**

Returns the documents in a Clicksign envelope, with each document's status, file name and download link.

- Action

**List Templates**

Returns the document templates (modelos) in your Clicksign account.

- Action

**Notifications Email**

Sends a signer a notification asking them to sign an envelope, with an optional custom message and email wording. Returns the notification and whether the signer was notified.

- Action

**Notifications SMS**

Re-sends the signing notification to a signer of an envelope, delivered over the channel the signer is set up for (SMS for SMS signers), with an optional custom message.

- Action

**Notifications WhatsApp**

Sends a reminder to a signer on an envelope through the WhatsApp channel configured for that signer, and returns whether the signer was notified.

- Action

**Remove Signer From Document**

Removes a signer who has not yet started signing from a Clicksign envelope.

- Action

**View Document**

Returns the current details and status of a document inside a Clicksign envelope.

- Action

**View Signer**

Returns the current details of a signer on a Clicksign envelope, including name, email, phone number and notification preferences.

## Each app on its own

- [ **Buildkite** Buildkite is a platform for running fast, secure, and scalable continuous integration pipelines on your own...](https://apiant.ai/connections/buildkite)
- [ **Clicksign** Clicksign is an electronic document signing platform that meets the requirements of integrity, authenticity...](https://apiant.ai/connections/clicksign)

Reviews

## What our customers say

## More from Buildkite

- [ **Buildkite to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/buildkite-to-hubspot)
- [ **Buildkite to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/buildkite-to-salesforce)
- [ **Buildkite to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/buildkite-to-slack)
- [ **Buildkite to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/buildkite-to-google-sheets)
- [ **Buildkite to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/buildkite-to-gmail)
- [ **Buildkite to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/buildkite-to-google-calendar)

## More into Clicksign

- [ **HubSpot to Clicksign** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-clicksign)
- [ **Salesforce to Clicksign** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-clicksign)
- [ **Slack to Clicksign** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-clicksign)
- [ **Google Sheets to Clicksign** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-clicksign)
- [ **Gmail to Clicksign** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-clicksign)
- [ **Google Calendar to Clicksign** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-clicksign)

Questions

## Buildkite and Clicksign, answered

###

### What can start an automation from Buildkite?

Any of Buildkite's 2 triggers in the catalog, including New build and Build finished. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Clicksign when something happens in Buildkite?

Any of Clicksign's 11 actions, including Create Signer, List Documents, List Templates and Notifications Email. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Clicksign to Buildkite?

Clicksign has no triggers in the catalog today, so automations start in Buildkite. If you need the other direction, ask: your agent reads Clicksign's API documentation and adds it.

###

### Do I have to build a connector for Buildkite or Clicksign?

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.

###

### Can my AI client use Buildkite and Clicksign without building an automation?

Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.

###

### 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.
