n8n

What the n8n node doesCopy Anchor Link

The SourceGeek node for n8n gives your workflows the same tools SourceGeek's chat uses. Each tool is an action in n8n, so a workflow can search candidates, companies and job postings, look up employee data, save results as sheets, score a sheet against a job description, turn it into a shortlist and work with your projects, without opening SourceGeek.

The node can also be used as a tool by n8n's AI Agent node, so an agent you build in n8n can call SourceGeek itself.

Installing the nodeCopy Anchor Link

The node is the community node package n8n-nodes-sourcegeek.

1. In n8n, open Settings and go to Community nodes
2. Click Install, enter n8n-nodes-sourcegeek and confirm
3. Add a step to a workflow and search for SourceGeek

Community nodes must be enabled on your n8n instance; see n8n's installation guide.

Connecting your workspaceCopy Anchor Link

The node signs in with an API key.

1. In SourceGeek, open Settings and go to Connected apps
2. Under API keys, click Create API key, give it a name (for example "n8n") and create it
3. Copy the key. It is shown only once
4. In n8n, create a SourceGeek API credential and paste the key into API Key. Leave Base URL as https://chat.sourcegeek.com

The key acts as you in that workspace: the node sees what you see and creates sheets and tasks as you. Treat it like a password. To use a different workspace, create a key in that workspace and add a second credential.

Available actionsCopy Anchor Link

Actions are grouped by resource:

• Search: fast and precision searches for candidates, companies and job postings, finding people or companies by criteria, enriching a person or company, and searching previously known candidates
• Employee Data: public profiles, company pages, job postings and their hiring teams, posts, comments and reactions, and contact details
• Sheet and Shortlist: create and read sheets and documents, list your recent ones, score candidates, create shortlists and read shortlist feedback
• Project: list your projects and their tasks, read a task and its result, plan tasks and start SourceGeek on them
• Memory and Workspace Context: remember, forget and list memories, and read and update your workspace context
• Occupation and Skill (ESCO): search occupations and skills and look them up
• Labour Market Statistics (CBS): search official Dutch statistics tables and fetch vacancies, employment and wage figures

Each action's required inputs are fields on the node; optional ones are under Additional Fields. The action returns the tool's result as the item's JSON, for the next step in your workflow. To keep a workflow running when one item fails, set On Error to Continue in the node's settings; the error is then returned on that item.

Searches return their results as CSV and don't save anything. To keep results in SourceGeek, pass them to Create sheet. Scoring can take a minute or two: when Score candidates reports that it is still running, read the sheet again later with Read sheet or document.

CreditsCopy Anchor Link

Searches, employee data lookups, enrichment and scoring use your workspace's credits, exactly as they do in SourceGeek, and each project task the node starts costs one chat run. Reading your sheets, memory, workspace context and projects, and planning tasks, is free. A workflow that runs often or on many items can use a lot of credits, so test it on a few items first. You can follow usage on the Usage tab in your workspace settings.

Where results appearCopy Anchor Link

Sheets and shortlists the node creates are saved in your workspace, where you can share them with your team, score them again or continue in SourceGeek. Tasks it starts run in a chat of their own and report back in SourceGeek, as when you start them in the app.

Seeing and revoking keysCopy Anchor Link

Open your workspace settings and go to Connected apps. Under API keys you see your keys and when each was last used (admins see every member's keys). Click Revoke to cut n8n off immediately; what the node created stays in the workspace.

If you used the previous version of the SourceGeek node, update it to version 2 and create a new key: keys from the old SourceGeek app no longer work.