---
title: "Connect Chaport and Greenhouse - APIANT.ai"
description: "When \"Chat Stage Updated (instant)\" fires in Chaport, your agent runs \"Add Attachment to Candidate\" in Greenhouse."
canonical: "https://apiant.ai/connect/chaport-to-greenhouse"
---

# Connect Chaport and Greenhouse

When **Chat Stage Updated (instant)** fires in [Chaport](https://apiant.ai/connections/chaport), your agent runs **Add Attachment to Candidate** in [Greenhouse](https://apiant.ai/connections/greenhouse), or **Application Updated** in Greenhouse to **Send a Message** in Chaport. Describe the whole flow and it is built, tested on every scenario and kept running.

Chaport **8** triggers Chaport **12** actions Greenhouse **15** triggers Greenhouse **30** actions

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

## What do you want Chaport and Greenhouse 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 Chaport and Greenhouse can do together

### From Chaport to Greenhouse

- When **Chat Stage Updated (instant)** in Chaport then **Add Attachment to Candidate** in Greenhouse
- When **New Chat Started** in Chaport then **Add Candidate Education** in Greenhouse

### From Greenhouse to Chaport

- When **Application Updated** in Greenhouse then **Send a Message** in Chaport
- When **Candidate Updated** in Greenhouse then **Create an Operator** in Chaport

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 Chaport and Greenhouse

## Triggers and actions 23 triggers · 42 actions

- Trigger

**Chat Closed (instant)**

Fires when a chat is closed. Webhook event: chat.closed.

- Trigger

**Chat Finished**

Triggers when chat is finished.

- Trigger

**Chat Stage Updated (instant)**

Fires when a chat's stage changes. Webhook event: chat.stageUpdated.

- Trigger

**Message Read (instant)**

Fires when a message is read. Webhook event: message.read.

- Trigger

**New Chat Started**

Triggers when chat is started.

- Trigger

**New Message Sent (instant)**

Fires when a new message is sent in a chat. Webhook event: message.sent.

- Trigger

**New Visitor (instant)**

Fires when a new visitor is created. Webhook event: visitor.created.

- Trigger

**Visitor Updated**

Triggers when visitor data is updated.

- Action

**Create an Operator**

Adds a new operator to your Chaport account and returns the created operator.

- Action

**Delete a Message**

Deletes one message from a Chaport chat. Identify the visitor and the message you want removed.

- Action

**Delete an Operator**

Removes an operator from your Chaport account.

- Action

**List Operators**

Returns every operator in your Chaport account, with each operator's name, email, role and status.

- Action

**List Visitors**

Returns the visitors in your Chaport account, one page at a time.

- Action

**Retrieve an Operator**

Returns one Chaport operator with their name, email, role, job title and current status.

- Action

**Retrieve a Visitor**

Returns one Chaport visitor with their name, contact details, notes and any custom data held about them.

- Action

**Retrieve Last Visitor Chat**

Returns a visitor's most recent Chaport chat, including its stage, operators and — when asked for — the transcript.

- Action

**Send a Message**

Posts a message into a Chaport visitor's chat, starting a chat if there isn't one open.

- Action

**Update an Operator**

Updates a Chaport operator's details. Anything you leave blank keeps its current value.

- Action

**Update a Visitor**

Updates an existing Chaport visitor's contact details, notes and custom data. Only the fields you fill in are changed; blank fields are left untouched.

- Action

**Update Operator Status**

Sets a Chaport operator's availability status, such as online or offline, optionally for a limited time.

- Trigger

**Application Rejected**

Triggers when an application in Greenhouse is rejected, returning the rejected application with its candidate, job, rejection reason and custom fields.

- Trigger

**Application Updated**

Triggers when an application is created or updated in Greenhouse, including stage moves, rejections and hires.

- Trigger

**Candidate Hired**

Triggers when a candidate's application is marked as hired in Greenhouse, delivering the hired application.

- Trigger

**Candidate Updated**

Triggers when a candidate is created or updated in Greenhouse, returning the candidate's profile, contact details, tags and custom fields.

- Trigger

**Job Updated**

Triggers when a job (hiring plan) is created or updated in Greenhouse.

- Trigger

**New Candidate**

Triggers when a new candidate or prospect is added to Greenhouse.

- Trigger

**New Candidate Application**

Triggers when a new application is submitted or added for a candidate in Greenhouse, optionally limited to specific jobs, stages, sources or statuses.

- Trigger

**New Job**

Triggers when a new job (requisition / hiring plan) is created in Greenhouse.

- Trigger

**New Job Post**

Triggers when a new job post (a candidate-facing listing of a job) is created in Greenhouse.

- Trigger

**New Note**

Triggers when a new note is added to a candidate's profile in Greenhouse, including logged emails and activity entries.

- Trigger

**New Offer**

Triggers when a new offer is created on a candidate's application in Greenhouse.

- Trigger

**New Scheduled Interview**

Triggers when an interview on a candidate's application is scheduled on the calendar in Greenhouse.

- Trigger

**New Scorecard**

Triggers when an interviewer submits a scorecard for a candidate's interview in Greenhouse.

- Trigger

**New Scorecard Due**

Triggers when an interview has taken place and the interviewer's scorecard is still in draft, waiting to be submitted.

- Trigger

**Offer Updated**

Triggers when an offer is created or updated in Greenhouse, including status changes such as accepted or rejected.

- Action

**Add Attachment to Candidate**

Attaches a file (resume, cover letter, offer letter or other document) to a candidate's application in Greenhouse, from a public file URL or base64 file content.

- Action

**Add Candidate Education**

Adds an education entry (school, degree, field of study and dates) to a candidate's profile in Greenhouse.

- Action

**Add Candidate Employment**

Adds a work history entry (employer, job title and dates) to a candidate's profile in Greenhouse. Leave the end date blank to record it as the candidate's current job.

- Action

**Add Tag to Candidate**

Applies an existing tag from your organization's tag list to a candidate. Returns the applied tag record.

- Action

**Convert Prospect to Candidate**

Converts a prospect application into a candidate application on a job, optionally placing it on a chosen interview stage. Returns the new candidate application.

- Action

**Create Application**

Creates a new application for an existing Greenhouse candidate, either on a job or as a prospect application.

- Action

**Create Candidate**

Creates a new candidate in Greenhouse, either applied to a job or as a prospect, and returns the new candidate and their application.

- Action

**Create Interview**

Records an interview that is already scheduled on an external calendar against a candidate's application, at a chosen slot on the job's interview plan. It does not create a calendar event or send invites.

- Action

**Create Job**

Creates a new job in Greenhouse from an existing template job, with the requested number of openings, department, offices and custom field values.

- Action

**Create Job Note**

Adds a note to a job in Greenhouse, written on behalf of the user you choose and visible to job admins or to users allowed to see private job notes.

- Action

**Create Offer**

Creates an offer on an existing Greenhouse application, with an optional start date, opening and offer/compensation custom field values.

- Action

**Create Opening**

Adds a new opening (headcount slot) to an existing Greenhouse job, optionally with your own position id and opening custom field values.

- Action

**Delete Application**

Permanently deletes a single application, along with its interview stages, scorecards and rejection details. The candidate and their other applications are kept.

- Action

**Delete Candidate**

Permanently deletes a candidate along with all of their applications, attachments, scorecards and notes. This cannot be undone.

- Action

**Delete Interview**

Cancels and deletes a scheduled interview in Greenhouse, along with its interviewer assignments and reminders. Only interviews that are scheduled or awaiting feedback can be deleted.

- Action

**Delete Note**

Permanently deletes a note from a candidate's activity feed. This cannot be undone.

- Action

**Delete Opening**

Permanently removes an opening from its job. Only closed openings with no offer and no hired application can be deleted.

- Action

**Find Application**

Returns up to 100 job applications that match a free-text search and/or filters such as candidate, job, stage, source, department, office or hiring team.

- Action

**Find Candidate**

Returns up to 100 candidates and prospects that match a free-text search and/or filters such as job, stage, tag, source or recruiter, plus the first match on its own.

- Action

**Find Due Scorecard**

Finds scorecards that are still due — interview evaluations an interviewer has not yet submitted — for the applications, interviewers or interview kits you specify.

- Action

**Find Job**

Returns up to 100 jobs matching a free-text search term and optional filters such as status, department, office, hiring team member or custom field answer.

- Action

**Find Offer**

Finds offers extended to candidates, filtered by application, candidate, job, opening, status or date, and returns the matching offers plus the first match.

- Action

**Merge Candidates**

Merges a duplicate candidate into another candidate. The primary candidate keeps its profile and absorbs the duplicate's applications, attachments, notes and tags; the duplicate is deleted.

- Action

**Move Application**

Moves an application to a different interview stage on the same job, or transfers it to another job. Stage transition rules, including automated emails, fire as they would in Greenhouse.

- Action

**Reject Application**

Rejects a candidate's application with a rejection reason, optionally sending the candidate a templated rejection email and setting application custom fields.

- Action

**Remove Tag from Candidate**

Removes a tag from a candidate by deleting the applied-tag record. The tag itself stays in your Greenhouse tag list.

- Action

**Unreject Application**

Reverses a rejection on an application, returning it to the in-process state on the stage it was rejected from. The earlier rejection reason and notes are cleared.

- Action

**Update Interview**

Updates a scheduled interview's time, location, video conferencing link, calendar event id, organizer or interviewer panel. Changes the Greenhouse record only and sends no calendar invites.

- Action

**Update Job Post**

Updates a Greenhouse job post: change its public title, replace its description, or publish it (live) or return it to draft.

- Action

**Update Opening**

Updates an opening on a Greenhouse job — its external id, target start date, custom fields, or open/closed status with a close reason.

## Each app on its own

- [ **Chaport** Chaport is a live chat for websites designed as a modern messenger.](https://apiant.ai/connections/chaport)
- [ **Greenhouse** Greenhouse is a hiring software company. We create the technology, know-how and support for your business'...](https://apiant.ai/connections/greenhouse)

Reviews

## What our customers say

## More from Chaport

- [ **Chaport to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/chaport-to-stripe)
- [ **Chaport to Chatrace** Omnichannel chatbot platform for automating customer support and sales via WhatsApp, SMS, Messenger...](https://apiant.ai/connect/chaport-to-chatrace)
- [ **Chaport to keycdn IP Location Finder** Get the IP geolocation data through the simple REST API. All the responses are JSON encoded](https://apiant.ai/connect/chaport-to-keycdn-ip-location-finder)
- [ **Chaport to ProxiedMail** ProxiedMail provides creating email addresses, forwarding and receiving emails with full context.](https://apiant.ai/connect/chaport-to-proxiedmail)
- [ **Chaport to Publica** With Publica, you can sell, share and consume all kinds of digital content directly through a reliable and...](https://apiant.ai/connect/chaport-to-publica)
- [ **Chaport to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/chaport-to-hubspot)

## More into Greenhouse

- [ **Google Sheets to Greenhouse** Google Sheets](https://apiant.ai/connect/google-sheets-to-greenhouse)
- [ **Gmail to Greenhouse** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-greenhouse)
- [ **Google Calendar to Greenhouse** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-greenhouse)
- [ **Google Drive to Greenhouse** Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...](https://apiant.ai/connect/google-drive-to-greenhouse)
- [ **ActiveCampaign to Greenhouse** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-greenhouse)
- [ **Airtable to Greenhouse** Organize anything with Airtable, a modern database created for everyone.](https://apiant.ai/connect/airtable-to-greenhouse)

Questions

## Chaport and Greenhouse, answered

###

### What can start an automation from Chaport?

Any of Chaport's 8 triggers in the catalog, including Chat Stage Updated (instant), New Chat Started, New Message Sent (instant) and New Visitor (instant). Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Greenhouse when something happens in Chaport?

Any of Greenhouse's 30 actions, including Create Application, Create Candidate, Create Interview and Create Job. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Greenhouse to Chaport?

Yes. When something happens in Greenhouse, your agent can act in Chaport too. This page covers both directions: Greenhouse's triggers and Chaport's actions are listed here as well.

###

### Do I have to build a connector for Chaport or Greenhouse?

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 Chaport and Greenhouse 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.
