Question 1

We already use Slack for review requests — why do we need this?

Accepted Answer

Slack is a channel, not a queue. There's no record, no escalation when someone's out, no SLA, and no way to see what's pending across every workflow at once. Humangent is the surface; Slack stays one of the channels reviewers can pick to be notified.

Question 2

Do my reviewers need n8n access?

Accepted Answer

No. Reviewers get a Humangent account and never see n8n. They open a request, see the context, choose an action, and the workflow resumes. Each reviewer picks their own delivery channel — Slack, email, Telegram, Teams — when they set up their account.

Question 3

What happens if a reviewer doesn't respond?

Accepted Answer

Configurable per request type. Auto-approve, auto-reject, or escalate to the next person or role on the chain. The workflow always continues — it never hangs.

Question 4

Can reviewers edit AI output before approving?

Accepted Answer

Yes. Mark any field as editable. A reviewer can rewrite a draft email, fix a dollar amount, correct a customer name — and the corrected version flows back into your workflow. Every edit is captured in the audit trail.

Question 5

How does my n8n team integrate it?

Accepted Answer

Drop in the dedicated Humangent node from the n8n catalog, or call us from a standard HTTP Request node + Wait for Webhook. Both work with n8n Cloud and self-hosted.

Question 6

Is this for compliance or regulated work?

Accepted Answer

The audit trail is built in — every decision has a record of who saw it, what they edited, who signed off, and when. We don't sell compliance export packs today, but the defensible decision record is there when you need to reconstruct what happened.

404

Page Not Found