The two payloads differ, so give each one its own workflow with its own Webhook node.
Webhooks are available on higher plans or as a paid add-on.
body, so fields read as body.projects, body.data and so on.
Job alerts
Step 1: Create a Webhook node
- Create a new workflow and add a Webhook node as the trigger.
- Set HTTP Method to
POST. - Click Listen for test event and copy the Test URL.
Step 2: Send a test from Vollna
- Go to Dashboard → Notifications and click Add notification.
- Pick Webhook and paste the Test URL into URL.
- Pick the filters that should send jobs.
- Click Send test. Vollna sends up to 3 recent jobs from those filters, and n8n shows them in the Webhook node.
Step 3: Switch to the Production URL
- In n8n, copy the node’s Production URL and publish the workflow.
- In Vollna, replace the URL with the Production URL and click Add notification.
Step 4: Run each job through the workflow
One request can carry several new jobs. To handle each job as its own item:- Add a Split Out node after the Webhook node.
- Set Field to Split Out to
body.projects. - Connect the nodes that should run once per job.
client_details.total_spent > 10000) → Slack posts jobs from clients who have spent more than $10,000 on Upwork, and the IF node drops the rest.
The job alert field reference lists every field.
Proposals and invitations
Step 1: Create a second workflow
- Create a new workflow with a Webhook node, set to
POST. - Click Listen for test event and copy the Test URL.
Step 2: Send a test from Vollna
- Go to Dashboard → Settings → Developers → Webhooks and click Add Endpoint.
- Paste the Test URL into Webhook URL.
- Under Events to receive, tick the events you need. Proposal Status Changed also lets you pick which statuses send an event.
- Click Send Test Request. Vollna sends your newest proposal, or your newest invitation if you picked only invitation events, and n8n shows it in the Webhook node.
Step 3: Switch to the Production URL
- In n8n, copy the node’s Production URL and publish the workflow.
- In Vollna, replace the URL with the Production URL and click Create Webhook.
Step 4: Map the event
Mapbody.event, body.timestamp and the fields under body.data, such as body.data.jobDetails.title and body.data.isViewed. The test request has the event webhook.test, so an IF node on body.event can drop it.
One request carries one event, so this workflow needs no Split Out.
The Team Webhooks payload shows every field. To trace repeated deliveries, log X-Vollna-Event-Id (the same value as body.id). To process each proposal once, key on body.data.applicationUid.
Troubleshooting
- The test works but live events don’t arrive. Publish the workflow and point Vollna at the Production URL. The Test URL works only while the editor listens.
- n8n answers 404. The path differs between the Test URL and the Production URL. Copy the exact URL from the Webhook node again.
- Fields come back empty. Read them under
body, for examplebody.filter.nameorbody.data.jobDetails.title. - The proposal test shows only
test,messageandwebhook_urlunderbody.data. You have no proposals or invitations in Vollna yet, so the test carries a test message. Send the test again after your first proposal syncs.