---
title: "Connect Greenhouse to Resend - APIANT.ai"
description: "When \"Application Updated\" fires in Greenhouse, your agent runs \"Add Contact to Segment\" in Resend."
canonical: "https://apiant.ai/connect/greenhouse-to-resend"
---

# Connect Greenhouse to Resend

When **Application Updated** fires in [Greenhouse](https://apiant.ai/connections/greenhouse), your agent runs **Add Contact to Segment** in [Resend](https://apiant.ai/connections/resend). Describe the whole flow and it is built, tested on every scenario and kept running.

Greenhouse **15** triggers Greenhouse **38** actions Resend **28** actions

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

## What do you want Greenhouse and Resend 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 Greenhouse can start in Resend

- When **Application Updated** in Greenhouse then **Add Contact to Segment** in Resend
- When **Candidate Updated** in Greenhouse then **Create Contact** in Resend

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

## Triggers and actions 15 triggers · 66 actions

- 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 Candidate Note**

Adds a note, logged email, or activity-feed entry to a Greenhouse candidate, optionally tied to one of their applications.

- 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 Job Post**

Creates a new job post by copying an existing job post onto a job board, optionally with a new title, description, and publication status.

- 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

**Create Prospect**

Creates a new prospect in Greenhouse: a candidate profile with a prospect application, optionally tied to jobs, a prospect pool, a department or an office.

- 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

**Hire Application**

Marks a candidate's application as hired and closes the matching opening on the job.

- 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 Application**

Updates the attribution and details of an existing Greenhouse application, such as its source, referrer, recruiter, coordinator, prospect pool and stage, and custom fields.

- Action

**Update Candidate**

Updates an existing Greenhouse candidate's profile — name, company, title, contact details, tags, linked users and custom fields. Only the values you fill in are changed.

- 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**

Updates an existing Greenhouse job's name, notes, offices, department, requisition id and custom fields, and returns the updated job.

- 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 Offer**

Updates an existing offer's start date, opening, sent/created/resolved dates and offer custom fields, including compensation. Returns the updated offer.

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

- Action

**Add Contact to Segment**

Adds a contact to a Resend segment. You can identify the contact by its ID or email address.

- Action

**Add Suppression**

Adds an email address to your Resend suppression list so no further mail is sent to it.

- Action

**Cancel Email**

Cancels a scheduled Resend email that has not been sent yet.

- Action

**Create API Key**

Creates a new Resend API key. The key itself is returned once, so store it right away.

- Action

**Create Contact**

Creates a contact in Resend. Returns the new contact's ID.

- Action

**Create Domain**

Adds a sending domain to Resend. Returns the DNS records you need to add at your domain host to verify it.

- Action

**Create Segment**

Creates a new segment in Resend for grouping contacts.

- Action

**Delete API Key**

Deletes a Resend API key so it can no longer be used.

- Action

**Delete Contact**

Deletes a contact from Resend. You can identify the contact by its ID or email address.

- Action

**Delete Domain**

Removes a sending domain from Resend.

- Action

**Delete Segment**

Deletes a segment from Resend. The contacts themselves are not deleted.

- Action

**List API Keys**

Returns the API keys on your Resend account, with each key's name and when it was last used. The key values themselves are never returned.

- Action

**List Contacts**

Returns the contacts in your Resend account, optionally limited to one segment.

- Action

**List Domains**

Returns the sending domains on your Resend account and each one's verification status.

- Action

**List Segments**

Returns the contact segments in your Resend account.

- Action

**List Sent Emails**

Returns the emails you have sent through Resend, newest first, with each email's id, sender, recipients, subject, send time and latest delivery event. Supports paging before or after a given email id.

- Action

**List Suppressions**

Returns the email addresses on your Resend suppression list, showing for each one the address, why it was suppressed (bounce, complaint or added manually), the email that triggered it and when it was added.

- Action

**Remove Contact From Segment**

Removes a contact from one of your Resend segments. Identify the contact by its ID or by its email address, and name the segment to take it out of. The contact itself is not deleted.

- Action

**Remove Suppression**

Takes an email address off your Resend suppression list so you can send to it again. Identify it by the suppression ID or by the email address itself.

- Action

**Retrieve Contact**

Returns one contact from your Resend audience, including their name, email address, whether they have unsubscribed, when they were added, and any custom properties stored on them. Look the contact up by its ID or by its email address.

- Action

**Retrieve Domain**

Returns one of your Resend sending domains, including its name, verification status, sending region, tracking settings and the DNS records it needs with each record's current status.

- Action

**Retrieve Segment**

Returns one of your Resend segments by its ID, with the segment's name and when it was created.

- Action

**Retrieve Sent Email**

Returns one email you sent through Resend, with its sender, recipients, subject, HTML and text body, tags, send time and latest delivery event.

- Action

**Send Batch Emails**

Sends up to 100 emails through Resend in a single call. Give it a list of emails, each with a sender, recipients, subject and body, and it returns the id of every email it created.

- Action

**Send Email**

Sends an email through Resend. Set the sender, recipients and subject, provide an HTML or plain text body, and optionally add CC/BCC, reply-to, attachments, tags or a send time.

- Action

**Update Contact**

Updates a contact in your Resend audience. Identify the contact by ID or email address, then change the name, the subscribed/unsubscribed state, or the custom properties. Anything you leave blank stays as it is.

- Action

**Update Email**

Reschedules an email you already queued in Resend, moving it to a new send date and time. Only emails that have not gone out yet can be changed.

- Action

**Verify Domain**

Asks Resend to re-check the DNS records for one of your sending domains and start verifying it. Verification runs in the background, so the domain shows as pending until it finishes.

## Each app on its own

- [ **Greenhouse** Greenhouse is a hiring software company. We create the technology, know-how and support for your business'...](https://apiant.ai/connections/greenhouse)
- [ **Resend** Resend is the email API for developers. It's designed for you to build, test, and send transactional and...](https://apiant.ai/connections/resend)

Reviews

## What our customers say

## More from Greenhouse

- [ **Greenhouse to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/greenhouse-to-hubspot)
- [ **Greenhouse to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/greenhouse-to-salesforce)
- [ **Greenhouse to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/greenhouse-to-slack)
- [ **Greenhouse to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/greenhouse-to-mailchimp)
- [ **Greenhouse to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/greenhouse-to-stripe)
- [ **Greenhouse to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/greenhouse-to-shopify)

## More into Resend

- [ **Documenso to Resend** Documenso is an open-source digital signing platform.](https://apiant.ai/connect/documenso-to-resend)
- [ **Google BigQuery to Resend** BigQuery is Google's serverless and highly scalable enterprise data warehouse, designed to make all your...](https://apiant.ai/connect/google-bigquery-to-resend)
- [ **HubSpot to Resend** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-resend)
- [ **Salesforce to Resend** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-resend)
- [ **Slack to Resend** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-resend)
- [ **Google Sheets to Resend** Google Sheets](https://apiant.ai/connect/google-sheets-to-resend)

Questions

## Greenhouse and Resend, answered

###

### What can start an automation from Greenhouse?

Any of Greenhouse's 15 triggers in the catalog, including Application Updated, Candidate Updated, Job Updated and New Candidate. Describe the moment in plain language and your agent picks the right one.

###

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

Any of Resend's 28 actions, including Create API Key, Create Contact, Create Domain and Create Segment. Your agent maps the data both ways and tests every scenario before it ships.

###

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

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

###

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

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