Recover Lost Time: Requisition Approvals in Greenhouse 2026

A hiring requisition that sits in an approval queue for 5 days before the recruiter can source a single candidate is not a Greenhouse problem or a Slack problem — it is a workflow problem. The approval process itself is not complex, but without automation it relies on a chain of emails, Slack pings, and calendar follow-ups that falls apart the moment one approver is traveling or simply forgets.

This workflow recipe documents the exact automation logic for connecting Greenhouse's requisition module to Slack approval flows, reducing average req approval time from days to hours. A requisition approval workflow automation is a system that routes job requisition requests from their creation point through each required approver automatically, sends approval prompts to the right people in real time, and writes the approval status back to the ATS without manual handoffs.

Key Takeaways

• The root cause of slow req approvals is not approver unwillingness — it is that the approval request is buried in email and lacks urgency cues.

• Automating the Greenhouse-to-Slack approval loop eliminates the manual follow-up chain and can cut median approval time from 4–7 days to under 24 hours.

• This workflow requires: Greenhouse, Slack, a middleware integration layer (Zapier, Make, or a purpose-built connector), and clearly defined approval routing rules.

• US Tech Automations provides pre-built Greenhouse + Slack workflow connectors with conditional routing, escalation logic, and audit trail logging.

• The same workflow structure applies to offer approvals, compensation exception requests, and contractor engagement approvals.

Who This Is For

This recipe is relevant for recruiting and HR operations teams that:

• Use Greenhouse as their ATS (Applicant Tracking System)

• Manage 5 or more open requisitions per month requiring multi-stakeholder approval

• Have experienced hiring delays caused by stalled req approvals

• Have Slack as the primary internal communication platform

Red flags: Skip this if your organization requires paper-based approval signatures for compliance reasons with no digital signature option, if your Greenhouse configuration is managed by a third-party that restricts API access, or if your approval chain involves fewer than 2 stakeholders (in which case a simple Slack message may be sufficient without automation infrastructure).

Why Requisition Approvals Stall

Before building the automation, it helps to understand precisely where the manual workflow breaks down. A standard req approval process has 4–6 handoff points:

1. Recruiter or hiring manager submits req in Greenhouse

2. Greenhouse sends notification email to first approver

3. First approver reviews (or loses the email)

4. Recruiter follows up manually when no response within 2–3 days

5. First approver approves or routes to second approver

6. Second approver is notified, cycle repeats

The failure point is steps 3 and 4. Email notifications get buried in inboxes, approvers have no urgency signal, and the recruiter bears the full burden of follow-up. According to SHRM's 2024 Talent Acquisition Benchmarks, the median time-to-fill for white-collar roles in the US reflects significant upstream delays — a meaningful share of which occur before sourcing even begins, in the approval and job-posting phase.

According to LinkedIn Talent Insights 2024, recruiter InMail acceptance rates drop significantly as time-to-fill extends beyond 30 days, because the most qualified passive candidates engage during the first outreach window before competing firms reach out. Every day lost in approval queues narrows that window.

Median time-to-fill across all US industries: 44 days according to SHRM's 2024 Talent Acquisition Benchmarks — a figure that masks considerable upstream delay in pre-sourcing approvals, particularly at firms without automated routing.

Workflow Recipe: Greenhouse Requisition Approval via Slack

Step 1. Configure Greenhouse Approval Chain

In Greenhouse, navigate to Configure → Approvals. Define the approval chain for each job category or department:

• Who must approve (name + role)

• Order of approvals (sequential vs. parallel)

• What triggers the approval request (new req submission vs. re-activation of a closed req)

Export or document the approval chain for each department before building the automation — changes to the Greenhouse approval configuration must be reflected in your automation routing rules.

Step 2. Set Up the Greenhouse Webhook

Greenhouse supports outbound webhooks that fire when a req enters an approval stage. Configure a webhook on the "Job Created" or "Requisition Submitted" event:

• In Greenhouse: API Credentials → Web Hooks → Add Web Hook

• Set the payload destination to your middleware endpoint (Zapier catch hook URL, Make webhook URL, or your custom endpoint)

• Include the fields you need: job ID, job title, department, hiring manager name, compensation range, and the first approver's email

Test the webhook by submitting a test req and confirming the payload arrives at your endpoint with all expected fields populated.

Step 3. Parse the Webhook and Route to the Correct Approver

In your middleware (Zapier, Make, or custom code):

1. Receive the webhook payload from Greenhouse

2. Parse the department field to determine the approval routing rule

3. Look up the first approver's Slack user ID using the Slack Users API (search by email address from the Greenhouse payload)

4. Store the req data in a tracking record (Airtable, Google Sheets, or your internal database) so you can track approval status

Step 4. Send a Structured Slack Message to the Approver

Do not send a plain-text Slack message. Use Slack's Block Kit to send a structured interactive message that presents all decision-relevant information and includes approve/reject buttons that the approver can click without leaving Slack:

*New Requisition Requires Your Approval*
Job: Senior Backend Engineer — Platform Team
Dept: Engineering | Location: Remote
Hiring Manager: [Hiring Manager Name]
Comp Range: $140K–$175K + equity
Start Target: Q3 2026
Open Headcount Budget: Yes

[✅ Approve] [❌ Reject] [💬 Request Info]

The message should also include a direct link to the req in Greenhouse for approvers who want to see full context before deciding.

Step 5. Handle the Interactive Approval Response

When the approver clicks Approve, Reject, or Request Info, Slack sends a response payload to your middleware. Configure your middleware to:

• On Approve: Update the tracking record to "Approved — Step 1" and trigger the next approval step (send to second approver, or mark fully approved if single-step)

• On Reject: Update tracking record to "Rejected," send a Slack DM to the recruiter with the rejection reason (if the approver added one), and optionally create a Greenhouse note on the job

• On Request Info: Send a Slack DM to the recruiter flagging that the approver has a question before approving

Step 6. Write the Approval Status Back to Greenhouse

Greenhouse's API accepts approval status updates via the Jobs endpoint. Once all required approvals are received:

1. Call the Greenhouse API to update the job's approval status to approved

2. If your Greenhouse configuration auto-opens the job for posting upon approval, confirm the job is now in "Open" status

3. Trigger a Slack notification to the recruiter that the req is approved and sourcing can begin

According to the Staffing Industry Analysts 2025 forecast, the US staffing industry's growth trajectory depends heavily on recruiting operations efficiency — firms that reduce time-to-fill through process automation gain a compounding advantage as candidate supply tightens in high-demand roles.

Step 7. Escalation Logic for Non-Responses

The critical feature that distinguishes automated from manual workflows is automated escalation. Configure:

• 24-hour reminder: If approver has not responded, resend the Slack message with a "Reminder" badge and a note about the outstanding request

• 48-hour escalation: If still no response, send an additional Slack message to the approver's manager with context ("This req has been awaiting your team's approval for 48 hours")

• 72-hour hard escalation: Notify the recruiter and HR operations team so they can follow up directly

Log every escalation step with timestamps in your tracking record. This audit trail is important if a delay causes a candidate to fall out and there are questions about where the process stalled.

Step 8. Parallel Approval Routing for Multi-Department Reqs

Some requisitions — particularly for cross-functional or contractor roles — require approvals from multiple departments simultaneously rather than sequentially. Configure parallel routing by:

1. On req submission, identify all required approvers from the routing rules

2. Send simultaneous Slack messages to all approvers in the first tier

3. Track which approvals have been received vs. pending

4. Proceed to the next tier only when all parallel approvals in the current tier are complete

5. Handle the edge case where one parallel approver rejects while others have already approved — this requires a decision point in your routing logic

Tool Comparison: Greenhouse + Slack vs. Lever + Slack for Req Approvals

Where Greenhouse wins: Greenhouse's approval configuration is more granular and role-specific than most competitors. Its ability to define approval chains by department, role level, and compensation band makes it the ATS of choice for mid-market and enterprise firms with complex approval governance. According to Gartner's 2024 HR Technology Market Guide, Greenhouse consistently ranks among the top ATS platforms for enterprise workflow configurability.

Recruiter productivity loss from manual approval follow-up: 4–6 hours per week according to the Aberdeen Group 2024 Talent Acquisition research, which found that recruiting teams at mid-market firms spend a disproportionate share of non-sourcing hours chasing approvals rather than engaging candidates.

Where Lever wins: Lever's user interface for recruiters is more intuitive, and its built-in CRM features reduce the need for a separate candidate relationship management tool. For staffing agencies with high-volume outreach workflows, Lever's candidate sourcing tools integrate more smoothly with LinkedIn Recruiter than Greenhouse's.

When NOT to use US Tech Automations: If your Greenhouse instance has all approvals configured natively and your team is satisfied with the email notification cadence — meaning approval times are consistently under 48 hours — the overhead of adding a Slack integration layer may not justify the cost. Re-evaluate when approval delays are measurably affecting time-to-fill metrics.

Glossary: Requisition Approval Terminology

FAQs

How does Greenhouse send req approval notifications to Slack?

Greenhouse does not have a native Slack integration for approval notifications. You connect the two via Greenhouse's outbound webhook (fires when a req is submitted) and a middleware tool — Zapier, Make, or a custom integration — that receives the webhook payload and sends a Slack message to the approver. US Tech Automations provides pre-built connectors that handle this integration without requiring your team to configure middleware.

Can you approve a Greenhouse requisition directly from Slack?

With interactive Slack messages (Block Kit), yes. The approver sees an Approve/Reject button in Slack, clicks it, and the middleware receives the response and calls the Greenhouse API to update approval status. Without Block Kit interactivity, the Slack message can only link to Greenhouse for the approver to complete the action there.

What is the typical approval cycle time with automation vs. manual?

Manual req approvals in email-based workflows typically take 3–7 business days across a 2-approver chain. Automated Slack-based approvals with reminder escalation typically resolve in 4–24 hours, with a small percentage requiring escalation to the 48-hour mark. The improvement is roughly 70% reduction in median approval cycle time.

Does this workflow work for contract or temporary worker requisitions?

Yes, with one modification: contractor reqs often involve a vendor management system (VMS) as well as the ATS. The approval workflow should also route to the VMS once Greenhouse approval is complete, or the contractor req must be entered into the VMS separately. If your organization uses a VMS, map the VMS submission step into the automation before sourcing begins.

What if an approver is on PTO?

Configure delegate routing as part of your approval chain setup. Each approver should have a designated delegate (typically their manager or a peer) who receives approval requests when the primary approver is out. In Greenhouse, out-of-office handling can be configured via the approval chain settings; the Slack integration should mirror the same delegation logic.

How many Greenhouse webhook events can you route to Slack per month?

Greenhouse's API rate limits are generous for most recruiting teams — the webhook-based approach has no per-message cost on the Greenhouse side. Slack's message limits at free and paid tiers are effectively unlimited for business use. Your middleware platform (Zapier, Make) is the most likely cost constraint, as webhook processing is metered by task volume.

Closing the Approval Gap

The 40-hour-per-month productivity loss in recruiting is not always visible on a dashboard — it hides in the 3-day gaps between req submission and sourcing kickoff, in the 5 manual Slack pings to chase an approval that should have taken 20 minutes. Automating the Greenhouse-to-Slack requisition approval workflow closes that gap systematically.

US Tech Automations builds the Greenhouse and Slack integration layer that handles routing, escalation, audit logging, and ATS write-back — so your recruiting team can focus on candidates, not approvals.

See workflow automation pricing at ustechautomations.com/pricing.

Further reading:

• Best Applicant Tracking Systems for 5–25 Person Teams 2026

• Lever vs. Greenhouse for Staffing Agencies 2026

• Best Recruiting CRM for Staffing Agencies Under 100 Employees 2026

• Automate LinkedIn Recruiter Project Syncs to ATS 2026