--- title: "Connect COR and Greenhouse - APIANT.ai" description: "When \"Create Brand\" fires in COR, your agent runs \"Create Candidate Note\" in Greenhouse, or \"Application Updated\" in Greenhouse to \"Create Invoice\" in COR." canonical: "https://apiant.ai/connect/cor-to-greenhouse" --- # Connect COR and Greenhouse When **Create Brand** fires in [COR](https://apiant.ai/connections/cor), your agent runs **Create Candidate Note** in [Greenhouse](https://apiant.ai/connections/greenhouse), or **Application Updated** in Greenhouse to **Create Invoice** in COR. Describe the whole flow and it is built, tested on every scenario and kept running. COR **12** triggers COR **24** actions Greenhouse **15** triggers Greenhouse **38** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want COR 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 COR and Greenhouse can do together ### From COR to Greenhouse - When **Create Brand** in COR then **Create Candidate Note** in Greenhouse - When **Create Client** in COR then **Add Attachment to Candidate** in Greenhouse ### From Greenhouse to COR - When **Application Updated** in Greenhouse then **Create Invoice** in COR - When **Candidate Updated** in Greenhouse then **Create Task** in COR 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 COR and Greenhouse ## Triggers and actions 27 triggers · 62 actions - Trigger **Create Brand** Triggers when a new brand is created in COR. - Trigger **Create Client** Triggers when a new client is created in COR. - Trigger **Create Hour** Triggers when a new time entry is logged in COR. - Trigger **Create Invoice** Triggers when a new transaction is recorded in COR. COR has no separate invoice record, so this watches all transactions, invoices included; use the type field to tell them apart. - Trigger **Create Product** Triggers when a new product is created in COR. - Trigger **Create Project** Triggers when a new project is created in COR. - Trigger **Create Task** Triggers when a new task is created in COR. Returns the new task's details. - Trigger **Create User** Triggers when a new user is created in COR. - Trigger **Updated Client** Triggers when an existing client is changed in COR. - Trigger **Updated Project** Triggers when an existing project is updated in COR. - Trigger **Updated Task** Triggers when a task is changed, such as a new title, status, priority or deadline. Also fires when a new task appears. - Trigger **Updated User** Triggers when a user in COR is created or changed, such as their name, email, role, position or labels. - Action **Add brand** Creates a new brand under a client in COR. - Action **Add team** Creates a new team in COR with a name and, optionally, a description and workspace. Returns the team that was created. - Action **Create Client** Creates a new client in COR with its company details and primary contact, and returns the new client's id. - Action **Create Fee** Creates a fee for a client in COR, with its name, estimate and work order, and optional details such as dates, status and currency. Returns the new fee. - Action **Create Hour** Logs a time entry against a task in COR and returns the new entry's id. - Action **Create Invoice** Creates an invoice (a COR transaction) for the given date, total and currency, optionally linked to a client, and returns the new transaction. - Action **Create Project** Creates a new project for a client in COR and returns the created project. - Action **Create Task** Creates a new task in COR, optionally within a project, and returns the created task. - Action **Delete Project** Deletes a project in COR by its ID. - Action **Delete task** Deletes a task in COR by its ID. - Action **Find clients by name** Returns the clients whose name matches the specified name. - Action **Find projects by name** Returns the COR projects whose name matches the name you search for, including each project's client, project manager, status and budget details. - Action **Get client** Returns a single COR client by its id, including its business name, contact details, website and description. - Action **Get project** Returns a single COR project by its id, including its client, project manager, dates, status, budget figures and assigned labels. An error occurs if the project is not found. - Action **Get task** Returns a single COR task by its id, including its title, project, deadline, status and priority. - Action **List clients** Returns all clients in the COR account, optionally narrowed by filter criteria. - Action **List fees** Returns the fees in the COR account, including each fee's name, estimate, status and dates. - Action **List hours** Returns the time entries logged in the COR account, optionally narrowed by date range, client, project, user, label or team, and sorted as you choose. - Action **List products** Returns all products in the COR account, each with its name, client and brand. - Action **List projects** Returns the company's projects, optionally narrowed by client, team, user, brand, product, dates, status, health or archived state. - Action **List tasks** Returns the tasks in your COR account, optionally narrowed by project, project manager, status and other criteria, and sorted the way you choose. - Action **List teams** Returns the teams in the COR workspace, including each team's name and description. - Action **Update Project** Updates an existing project in COR, changing only the fields you fill in, and returns the updated project. - Action **Update Task** Updates an existing task by its id, changing its title, project, description, deadline, status, priority or archived state, and returns the updated task. - 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. ## Each app on its own - [ **COR** COR is the all-in-one management solution for creative agencies that automate timesheets, through AI, to...](https://apiant.ai/connections/cor) - [ **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 COR - [ **COR to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/cor-to-hubspot) - [ **COR to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/cor-to-salesforce) - [ **COR to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/cor-to-slack) - [ **COR to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/cor-to-google-sheets) - [ **COR to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/cor-to-gmail) - [ **COR to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/cor-to-google-calendar) ## More into Greenhouse - [ **Google Sheets to Greenhouse** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](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 ## COR and Greenhouse, answered ### ### What can start an automation from COR? Any of COR's 12 triggers in the catalog, including Create Brand, Create Client, Create Hour and Create Invoice. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Greenhouse when something happens in COR? Any of Greenhouse's 38 actions, including Create Application, Create Candidate, Create Candidate Note and Create Interview. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Greenhouse to COR? Yes. When something happens in Greenhouse, your agent can act in COR too. This page covers both directions: Greenhouse's triggers and COR's actions are listed here as well. ### ### Do I have to build a connector for COR 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 COR 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.