Integration
Connect Greenhouse and PDQ Connect
When Application Updated fires in Greenhouse, your agent runs Add group in PDQ Connect, or New Deployment in PDQ Connect to Create Candidate Note in Greenhouse. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Greenhouse and PDQ Connect to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)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)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)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
Setup guide (opens in a new tab)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)Example flows
What Greenhouse and PDQ Connect can do together
From Greenhouse to PDQ Connect
When Application Updated in Greenhouse
then Add group in PDQ Connect
When Candidate Updated in Greenhouse
then Create Custom Field in PDQ Connect
From PDQ Connect to Greenhouse
When New Deployment in PDQ Connect
then Create Candidate Note in Greenhouse
When New Device in PDQ Connect
then Add Attachment to Candidate in Greenhouse
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 PDQ Connect
Triggers and actions 24 triggers · 55 actions
Trigger
Application RejectedTriggers when an application in Greenhouse is rejected, returning the rejected application with its candidate, job, rejection reason and custom fields.
Trigger
Application UpdatedTriggers when an application is created or updated in Greenhouse, including stage moves, rejections and hires.
Trigger
Candidate HiredTriggers when a candidate's application is marked as hired in Greenhouse, delivering the hired application.
Trigger
Candidate UpdatedTriggers when a candidate is created or updated in Greenhouse, returning the candidate's profile, contact details, tags and custom fields.
Trigger
Job UpdatedTriggers when a job (hiring plan) is created or updated in Greenhouse.
Trigger
New CandidateTriggers when a new candidate or prospect is added to Greenhouse.
Trigger
New Candidate ApplicationTriggers when a new application is submitted or added for a candidate in Greenhouse, optionally limited to specific jobs, stages, sources or statuses.
Trigger
New JobTriggers when a new job (requisition / hiring plan) is created in Greenhouse.
Trigger
New Job PostTriggers when a new job post (a candidate-facing listing of a job) is created in Greenhouse.
Trigger
New NoteTriggers when a new note is added to a candidate's profile in Greenhouse, including logged emails and activity entries.
Trigger
New OfferTriggers when a new offer is created on a candidate's application in Greenhouse.
Trigger
New Scheduled InterviewTriggers when an interview on a candidate's application is scheduled on the calendar in Greenhouse.
Trigger
New ScorecardTriggers when an interviewer submits a scorecard for a candidate's interview in Greenhouse.
Trigger
New Scorecard DueTriggers when an interview has taken place and the interviewer's scorecard is still in draft, waiting to be submitted.
Trigger
Offer UpdatedTriggers when an offer is created or updated in Greenhouse, including status changes such as accepted or rejected.
Action
Add Attachment to CandidateAttaches 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 EducationAdds an education entry (school, degree, field of study and dates) to a candidate's profile in Greenhouse.
Action
Add Candidate EmploymentAdds 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 CandidateApplies an existing tag from your organization's tag list to a candidate. Returns the applied tag record.
Action
Convert Prospect to CandidateConverts 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 ApplicationCreates a new application for an existing Greenhouse candidate, either on a job or as a prospect application.
Action
Create CandidateCreates 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 NoteAdds a note, logged email, or activity-feed entry to a Greenhouse candidate, optionally tied to one of their applications.
Action
Create InterviewRecords 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 JobCreates 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 NoteAdds 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 PostCreates 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 OfferCreates an offer on an existing Greenhouse application, with an optional start date, opening and offer/compensation custom field values.
Action
Create OpeningAdds a new opening (headcount slot) to an existing Greenhouse job, optionally with your own position id and opening custom field values.
Action
Create ProspectCreates 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 ApplicationPermanently deletes a single application, along with its interview stages, scorecards and rejection details. The candidate and their other applications are kept.
Action
Delete CandidatePermanently deletes a candidate along with all of their applications, attachments, scorecards and notes. This cannot be undone.
Action
Delete InterviewCancels 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 NotePermanently deletes a note from a candidate's activity feed. This cannot be undone.
Action
Delete OpeningPermanently removes an opening from its job. Only closed openings with no offer and no hired application can be deleted.
Action
Find ApplicationReturns 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 CandidateReturns 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 ScorecardFinds scorecards that are still due — interview evaluations an interviewer has not yet submitted — for the applications, interviewers or interview kits you specify.
Action
Find JobReturns 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 OfferFinds offers extended to candidates, filtered by application, candidate, job, opening, status or date, and returns the matching offers plus the first match.
Action
Hire ApplicationMarks a candidate's application as hired and closes the matching opening on the job.
Action
Merge CandidatesMerges 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 ApplicationMoves 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 ApplicationRejects 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 CandidateRemoves a tag from a candidate by deleting the applied-tag record. The tag itself stays in your Greenhouse tag list.
Action
Unreject ApplicationReverses 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 ApplicationUpdates 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 CandidateUpdates 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 InterviewUpdates 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 JobUpdates an existing Greenhouse job's name, notes, offices, department, requisition id and custom fields, and returns the updated job.
Action
Update Job PostUpdates a Greenhouse job post: change its public title, replace its description, or publish it (live) or return it to draft.
Action
Update OfferUpdates an existing offer's start date, opening, sent/created/resolved dates and offer custom fields, including compensation. Returns the updated offer.
Action
Update OpeningUpdates an opening on a Greenhouse job — its external id, target start date, custom fields, or open/closed status with a close reason.
Trigger
Matching Custom FieldTriggers for each PDQ custom field matching your filters on each poll, including ones that already exist.
Trigger
Matching DeploymentTriggers for each PDQ deployment matching your filters on each poll, with its status counts as first seen.
Trigger
Matching DeviceTriggers for each PDQ device matching your filters on each poll, including devices that already exist.
Trigger
Matching GroupTriggers for each PDQ group matching your filters on each poll, including groups that already exist.
Trigger
Matching PackageTriggers for each package in your PDQ library matching your filters on each poll, including existing ones.
Trigger
New DeploymentTriggers when a new deployment is created in PDQ.
Trigger
New DeviceTriggers when a new device is enrolled in PDQ.
Trigger
New GroupTriggers when a new device group is created in PDQ.
Trigger
New PackageTriggers when a new package is added to your PDQ library.
Action
Add groupCreates a static device group in PDQ Connect, optionally adding devices to it.
Action
Clear device custom field valueClears the value of a custom field on a device. The custom field itself is not deleted.
Action
Create Custom FieldCreates a new custom field definition in PDQ that devices can hold a value for.
Action
Delete custom fieldDeletes a custom field definition and removes its values from all devices.
Action
Delete groupDeletes a static group in PDQ Connect. The devices in the group are kept; only their membership is removed.
Action
Deploy PackageDeploys a package version to the PDQ devices and/or groups you list.
Action
Find Deployment by IDReturns one PDQ deployment by its ID with its current task status counts.
Action
Find DeviceFinds the first device in your PDQ organization whose name or hostname matches. Use ^value for starts-with or ~value for contains.
Action
Find Device by IDReturns one device in your PDQ organization by its ID, with its hardware, OS, user and network details.
Action
Find Device GroupFinds the first device group in PDQ whose name matches.
Action
Find Device VulnerabilitiesReturns the vulnerabilities detected on one PDQ device, optionally filtered by status or risk score.
Action
Find PackageFinds the first package in your PDQ library whose name or publisher matches.
Action
Find Package by IDReturns one package from your PDQ library by its ID, including its latest version.
Action
List device softwareReturns the software installed on a PDQ Connect device, with name, publisher, version and install details.
Action
Set Device Custom Field ValueSets the value of a custom field on one PDQ device.
Action
Update custom fieldRenames an existing custom field definition in PDQ Connect.
Action
Update groupRenames a static device group and/or replaces its device membership.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Greenhouse
Greenhouse to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Greenhouse to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Greenhouse to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Greenhouse to MailchimpMailchimp marketing automation and email platform.
Greenhouse to StripeStripe is a payment processing platform for online businesses.
Greenhouse to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into PDQ Connect
HubSpot to PDQ ConnectHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to PDQ ConnectGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to PDQ ConnectGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PDQ ConnectGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to PDQ ConnectGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to PDQ ConnectMailchimp marketing automation and email platform.
Questions
Greenhouse and PDQ Connect, 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 PDQ Connect when something happens in Greenhouse?
Any of PDQ Connect's 17 actions, including Create Custom Field, Update custom field, Update group and Add group. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from PDQ Connect to Greenhouse?
Yes. When something happens in PDQ Connect, your agent can act in Greenhouse too. This page covers both directions: PDQ Connect's triggers and Greenhouse's actions are listed here as well.
Do I have to build a connector for Greenhouse or PDQ Connect?
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 PDQ Connect 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.