--- title: "Connect Greenhouse to Maildroppa - APIANT.ai" description: "When \"Application Updated\" fires in Greenhouse, your agent runs \"Add or Update Subscriber Field (By Email)\" in Maildroppa." canonical: "https://apiant.ai/connect/greenhouse-to-maildroppa" --- # Connect Greenhouse to Maildroppa When **Application Updated** fires in [Greenhouse](https://apiant.ai/connections/greenhouse), your agent runs **Add or Update Subscriber Field (By Email)** in [Maildroppa](https://apiant.ai/connections/maildroppa). Describe the whole flow and it is built, tested on every scenario and kept running. Greenhouse **15** triggers Greenhouse **38** actions Maildroppa **31** 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 Maildroppa 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 Maildroppa - When **Application Updated** in Greenhouse then **Add or Update Subscriber Field (By Email)** in Maildroppa - When **Candidate Updated** in Greenhouse then **Add or Update Subscriber Field (By Subscriber ID)** in Maildroppa 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 Maildroppa ## Triggers and actions 15 triggers · 69 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 or Update Subscriber Field (By Email)** Sets (replaces) one custom field value on the subscriber with the given email address. - Action **Add or Update Subscriber Field (By Subscriber ID)** Sets or replaces one custom field value on a subscriber identified by subscriber ID. - Action **Assign Subscriber Tag (By Email)** Assigns a customer tag to the subscriber with the given email address. - Action **Assign Subscriber Tag (By Subscriber ID)** Assigns one of your active customer tags to a subscriber, identified by subscriber ID. Assigning a tag the subscriber already has does nothing. - Action **Count Subscribers (Filtered)** Returns the number of subscribers matching a set of segment conditions, optionally limited to one subscriber status. - Action **Create Field Type** Creates a custom subscriber field in Maildroppa, such as a text, number, date or choice field. - Action **Create Segment** Creates a subscriber segment in Maildroppa from a set of field, tag, topic, segment or purchase conditions. - Action **Create Tag** Creates a new tag in Maildroppa that can be assigned to subscribers and used in segments. - Action **Delete All Subscribers (Optionally by Status)** Deletes all subscribers in the account, optionally only those with a given status. Deletion runs in the background. - Action **Delete Field Type** Archives a customer-created subscriber field so it is no longer active. - Action **Delete Segment** Deletes a segment from your Maildroppa account. Segments still in use cannot be deleted. - Action **Delete Subscriber by Email** Deletes a subscriber from your Maildroppa audience, identified by their email address. - Action **Delete Subscriber by ID** Deletes a single subscriber from your Maildroppa account by their subscriber ID. - Action **Delete Subscriber Field (By Email)** Clears the value of one subscriber field for the subscriber with the given email address. - Action **Delete Subscriber Field (By Subscriber ID)** Clears the value of one subscriber field for the subscriber with the given ID. - Action **Delete Subscribers (Bulk)** Deletes several Maildroppa subscribers at once by their subscriber IDs. - Action **Delete Subscriber Tag (By Email)** Removes a customer tag from the subscriber with the given email address. - Action **Delete Subscriber Tag (By Subscriber ID)** Removes a tag from a subscriber identified by their subscriber ID. - Action **Delete Tag** Deletes (archives) a customer tag in Maildroppa so it can no longer be assigned. An archived tag can be restored later. - Action **Find Subscriber by Email** Finds a subscriber by their exact email address and returns their details. - Action **Get Segment by ID** Returns one Maildroppa segment by its ID, including its name and filter conditions. - Action **Get Subscriber by ID** Returns a subscriber by ID, including field values, tags, status and registration details. - Action **List Field Types (Paged)** Returns all subscriber fields in the Maildroppa account, both built-in and custom, including field types and choice options. - Action **List Filtered Subscribers (Paged)** Returns one page of subscribers matching a filter of field, tag, topic, segment or purchase conditions. - Action **List Tags** Returns the tags in your Maildroppa account, including system-managed tags, optionally with archived ones. - Action **Request Double Opt‑In** Starts double opt-in for a new subscriber by sending them a confirmation email. Their profile, tags and topics are applied once they confirm. - Action **Update Field Type** Updates a custom subscriber field's label, required flag, internal visibility, position and choice options. - Action **Update Segment** Replaces a segment's name and rules in Maildroppa. - Action **Update Subscriber** Updates a subscriber's email, first name, status, custom field values and tags. Values left blank keep the subscriber's current data. - Action **Update Subscriber Email** Changes the email address of an existing Maildroppa subscriber. - Action **Update Tag** Renames an existing customer tag in Maildroppa and returns the updated tag. ## 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) - [ **Maildroppa** Maildroppa is a B2B email-marketing platform that lets you create, send and track campaigns, manage...](https://apiant.ai/connections/maildroppa) 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 Maildroppa - [ **HubSpot to Maildroppa** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-maildroppa) - [ **Salesforce to Maildroppa** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-maildroppa) - [ **Slack to Maildroppa** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-maildroppa) - [ **Google Sheets to Maildroppa** Google Sheets](https://apiant.ai/connect/google-sheets-to-maildroppa) - [ **Gmail to Maildroppa** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-maildroppa) - [ **Google Calendar to Maildroppa** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-maildroppa) Questions ## Greenhouse and Maildroppa, 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 Maildroppa when something happens in Greenhouse? Any of Maildroppa's 31 actions, including Create Field Type, Create Segment, Create Tag and Update Field Type. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Maildroppa to Greenhouse? Maildroppa has no triggers in the catalog today, so automations start in Greenhouse. If you need the other direction, ask: your agent reads Maildroppa's API documentation and adds it. ### ### Do I have to build a connector for Greenhouse or Maildroppa? 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 Maildroppa 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.