Description

n8n-nodes-cavuno

This is an n8n community node for Cavuno job boards. It
lets you manage jobs, companies, candidates, and marketing permissions through
the Cavuno Operator API, and start workflows from signed Cavuno webhooks.

n8n is a fair-code licensed
workflow automation platform.

Installation

n8n Cloud

Cavuno is a verified community node on n8n Cloud. An instance owner or admin
can install it directly from a workflow:

1. Open the canvas and select + to open the nodes panel.
2. Search for Cavuno.
3. Under More from the community, select Cavuno, then select
Install.

If Cavuno does not appear, enable Verified Community Nodes in the
n8n Cloud Admin Panel, then restart the
instance if needed. Once installed, every member of the instance can use the
node.

Self-hosted n8n

Install Cavuno from the canvas when verified community nodes are enabled, or
open Settings → Community nodes → Install a community node and enter the
package name n8n-nodes-cavuno.

See n8n’s community node installation and management guide
for other installation methods and configuration options.

Credentials

Create an API key in your Cavuno dashboard under
Settings → Developer → API keys, then add
a Cavuno API credential in n8n:

• API Key — the cavunolive... key. Grant it only the scopes you need:

– Actions: the matching family scopes (jobs.read, jobs.manage,
jobs.publish, companies.read, companies.manage, candidates.read,
candidates.manage, marketing_permissions.read,
marketing_permissions.manage).
– Trigger: webhooks.read and webhooks.manage, plus the read scope of
each event family you subscribe to (for example jobs.read for job
events).

Company → Find needs only companies.read for ID or name lookups. Website
lookup uses Cavuno’s domain matcher and also needs companies.manage, as does
Find or Create.

Webhooks and API access are available on paid Cavuno plans. The node always
uses Cavuno’s canonical Operator API at https://api.cavuno.com/v1; there is
no board-specific base URL to enter.

Operations

Cavuno node:

• Job — Create, Get, Get Many, Update, Delete, Publish, Expire
• Company — Create, Find, Find or Create, Get, Get Many, Update, Delete
• Candidate — Get, Get Many, Delete
• Marketing Permission — Get Many (exact-match email lookup), Withdraw

Withdrawing marketing consent is safe to run more than once. Consent can only
be given by the person themselves on your board, so this node cannot grant
it.

Company fields are searchable selectors. Choose From List to find a
company by name, or By ID to paste an ID or use an expression. **Company →
Find** accepts a company ID, website, or exact name without creating a record.

Action errors show Cavuno’s own explanation. A 402 response also tells you
to upgrade the board’s plan; 401 identifies an invalid, expired, or revoked
API key.

Cavuno Trigger

The Cavuno Trigger node subscribes to your board’s outbound webhooks.
When the workflow is published it registers a webhook endpoint with the
selected events; unpublishing removes the endpoint again. Older n8n versions
call these actions Activate and Deactivate.

Available events: job.created, job.updated, job.deleted,
company.created, company.updated, company.deleted,
candidate.created, candidate.updated, candidate.deleted,
marketingpermission.granted, marketingpermission.withdrawn.

Cavuno only delivers to publicly reachable HTTPS URLs. On n8n Cloud this
just works; on current self-hosted n8n, set the N8NWEBHOOKURL environment
variable to your instance’s public HTTPS address before publishing the
workflow. Older n8n versions use WEBHOOK_URL.

Every delivery is verified before your workflow runs, following the
Standard Webhooks specification: the
node checks the webhook-id, webhook-timestamp (five-minute tolerance),
and HMAC-SHA256 webhook-signature headers against the endpoint’s signing
secret. Unverified requests are rejected and never reach your workflow.

Deliveries are retried by Cavuno until acknowledged, so your workflow may
occasionally receive the same event twice. If running twice would cause a
problem, deduplicate on the top-level id field. Each event also carries
data.object.revision — ignore events whose revision is not newer than the
last one you applied for that resource.

The trigger output keeps the original Cavuno envelope (occurred_at,
board_id, and data) for existing workflows and also adds mapping-friendly
fields: occurredAt, boardId, changedFields, and the resource snapshot as
resource. The top-level object: "event" discriminator is unchanged.

Compatibility

Requires n8n 1.x or later. No runtime dependencies.

Resources

• Cavuno API documentation
• n8n community nodes documentation

License

MIT