n8n

Praxicraft Assess is a verified community node on n8n. It gives you a Trigger (signed events from Assess) and Actions (invite candidates, list assessments, enroll pipelines, and more) — no custom webhook code required. Package: @praxicraft/n8n-nodes-assess

​

Prerequisites

• An n8n Cloud or self-hosted instance
• An Assess API key (Starter+) from Developer → API Keys — see Authentication

​

Setup guide

​

1. Create a workflow

Open n8n and create a new workflow. Click Add first step… on the canvas.

​

2. Open the trigger picker

n8n opens What triggers this workflow? Choose On app event (or search for the node directly).

​

3. Search for Praxicraft Assess

Type prax (or Praxicraft) in the search box. Select Praxicraft Assess — the verified checkmark means it is the official Assess node.

​

4. Confirm the verified node

Open the node details. You should see Verified, Installed (or Install), and the list of Assess triggers and actions.

​

5. Add credentials

1. Create an API key in Assess (Developer → API Keys).
2. On any Praxicraft Assess node, open Credential to connect with → Create new credential (or pick an existing one).

3. Paste your API key. Live keys start with ct_live_; test keys start with ct_test_. Leave Base URL as https://assess.praxicraft.com unless you use a custom host.
4. Save. n8n tests the credential with GET /org/ (needs organisation:read or a full-access key).

​

6. Build and run

Trigger path: pick an event (for example On candidate passed) → connect Slack, email, or your ATS. Action path: start from a manual trigger or ATS webhook → add Praxicraft Assess → choose an action such as List assessments.

​

7. Activate

Turn the workflow Active. For Trigger nodes, n8n registers a webhook with Assess, runs a test ping, and verifies X-Praxicraft-Signature for you.

​

If you are recruiting / ops

You need a technical teammate once for the API key and credentials. After that, edit workflows visually:

​

For engineers

​

Trigger behaviour

On activate: POST /webhooks/create/ → POST /webhooks/{id}/test/ → stores whsec_… → verifies X-Praxicraft-Signature. On deactivate, the webhook is deleted. webhook.test is ignored by default so pings do not run the workflow. High-value events: assessment.completed, candidate.passed / failed, pipeline.advanced / completed / rejected, interview.completed / analysis_ready.

​

Actions

Assessment, Case, Invitation, Pipeline (Reject / Hold / Unhold), Webhook (including Retry delivery via POST /webhooks/{id}/deliveries/{delivery_id}/retry/), Organisation, Interview, Integration — matching Public API capabilities. Destinations (HTTPS / Slack / Teams) use the Webhook resource.

​

Troubleshooting

​

Next

Automations · Zapier · Webhooks · Scopes · Authentication