Connect Greenhouse to Mx Technologies

Both apps 80Greenhouse 45Mx Technologies 35

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

• Action
  Add account

  Creates a manual account for an MX user. Manual accounts sit under the Manual Institution member and never aggregate data from a financial institution.

• Action
  Add budget

  Creates a budget for a category on an MX user.

• Action
  Add category

  Create a custom category for a user.

• Action
  Add goal

  Create a goal for a user.

• Action
  Add member

  Create a member (connection between a user and a financial institution) to start aggregation.

• Action
  Add transaction

  Creates a manual transaction on a manual account belonging to an MX user.

• Action
  Add user

  Creates a new MX user. The returned user guid is what other MX actions (such as Add member) use to identify the user.

• Action
  Aggregate member

  Starts an aggregation for a member, pulling the latest account and transaction data from the connected institution. MX may skip the aggregation if the data was updated recently.

• Action
  Delete account

  Delete a manually created account.

• Action
  Delete budget

  Deletes a budget belonging to an MX user.

• Action
  Delete category

  Delete a custom category.

• Action
  Delete goal

  Delete a goal.

• Action
  Delete member

  Delete a member connection.

• Action
  Delete user

  Delete a user.

• Action
  Get account

  Read an account's attributes.

• Action
  Get budget

  Retrieves a specific budget for an MX user.

• Action
  Get institution

  Read an institution's attributes.

• Action
  Get member

  Read a member's attributes and connection status.

• Action
  Get merchant

  Returns information about a particular merchant, such as its logo, name, and website.

• Action
  Get transaction

  Read a transaction's attributes.

• Action
  Get user

  Retrieves the attributes of a specific MX user.

• Action
  List accounts

  Lists all accounts belonging to an MX user. Returns up to 1000 accounts in one call.

• Action
  List categories

  Lists all categories for an MX user, including default and custom categories.

• Action
  List goals

  Lists all goals for an MX user.

• Action
  List institutions

  Lists financial institutions available through MX, optionally filtered by name, country and supported product.

• Action
  List members

  List all members belonging to a user.

• Action
  List merchants

  Lists merchants in the MX system, optionally filtered by a name substring.

• Action
  List transactions

  List all transactions for a user.

• Action
  Update account

  Updates an account belonging to a member. Manual accounts can have every field updated; aggregated accounts only accept changes to Is Business, Is Hidden and Metadata.

• Action
  Update budget

  Update a specific budget.

• Action
  Update category

  Update a custom category.

• Action
  Update goal

  Updates an existing savings or payoff goal for an MX user. Only the fields you fill in are changed.

• Action
  Update member

  Updates a member's credentials, id, metadata, background aggregation setting or use cases. At least one value to update must be supplied.

• Action
  Update transaction

  Update a transaction's category, description, or other editable attributes.

• Action
  Update user

  Update a user's attributes.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.