Zapier

Praxicraft Assess is a Zapier app with a New Assess Event trigger and actions for invites, results, pipelines, interviews, and more. Setup docs live here. The integration source is github.com/praxicraft-platform/zapier-praxicraft-assess.

​

Prerequisites

• A Zapier account
• An Assess API key (Starter+) from Developer → API Keys — see Authentication

​

Setup guide

​

1. Create a Zap

In Zapier, create a Zap. Skip Copilot and click the Trigger step.

​

2. Search for Praxicraft Assess

Open Apps and type pr (or Praxicraft). Select Praxicraft Assess.

​

3. Choose the trigger

Set Trigger event to New Assess Event, then Sign In to connect Assess.

​

4. Connect your account

Zapier opens Connect to Zapier:

1. Create an API key in Assess (Developer → API Keys).
2. Paste it into API Key. Keys start with ct_live_ (live) or ct_test_ (test). Use a test key while you build the Zap so live candidates are not emailed.
3. Leave Base URL as https://assess.praxicraft.com unless you use a custom host.
4. Click Connect. Zapier tests the connection with GET /org/ (needs organisation:read or a full-access key).

After a successful connect, the account appears on the trigger (for example your organisation name). Click Continue.

​

5. Pick the Assess event

On Configure, choose one event per Zap (for example assessment.completed or candidate.passed). When you turn the Zap on, Assess registers Zapier’s hook URL and sends a test ping. webhook.test pings do not run the Zap.

​

6. Add an action

Add a second step. Search Praxicraft Assess again to invite, enroll, or attach cases — or pick Slack, email, or your ATS.

​

7. Turn the Zap on

Inactive Zaps do not receive events. Turning a Zap off deletes the Assess webhook for that Zap.

​

If you are recruiting / ops

You need a technical teammate once for the API key. After that, edit Zaps visually: Prefer a Slack destination in Assess (Connect Slack, or an Incoming Webhook URL) for pass/fail alerts. Use Zapier’s Slack app when you need extra Zap steps (email, ATS, spreadsheets).

​

For engineers

​

Trigger behaviour

On enable: POST /webhooks/create/ with Zapier’s hook URL and the selected event, then POST /webhooks/{id}/test/. On disable, the destination is deleted. webhook.test pings do not run the Zap. Assess still signs bodies (X-Praxicraft-Signature). Zapier owns the hook URL — treat it as a trusted destination. You do not need to verify HMAC inside the Zap. High-value events: assessment.completed, candidate.passed / failed, pipeline.advanced / completed / rejected, interview.completed / analysis_ready. Full list: Webhooks.

​

Actions

Assessment, Case, Invitation, Pipeline, Webhook (including Retry delivery), Organisation, Interview, Integration — matching the n8n node and the Public API. Creates are writes; searches are GET / list. Destinations (HTTPS / Slack / Teams) use the Webhook resource. Optional external_id on Invite Candidate stores your ATS candidate id so retries do not create a second invite.

​

Troubleshooting

​

Next

Automations · n8n · Webhooks · Authentication