Your board can post directly into Slack and Discord channels ("New job published: Senior React Developer at Acme") and can trigger Zapier workflows, all through the same webhooks system, with no add-ons or third-party connectors. This article walks through each of the three, click by click. All of them start from the same place: in the sidebar, open Distribution and click Webhooks.
Post events to a Slack channel
First, get an incoming webhook URL from Slack:
In Slack, create (or open) an app for your workspace at api.slack.com/apps, enable Incoming Webhooks, and add a new webhook pointing at the channel you want (for example #new-jobs).
Copy the webhook URL Slack gives you. It starts with
https://hooks.slack.com/services/.
Then, in easyboard:
In the sidebar, open Distribution and click Webhooks, then click Add endpoint.
Enter a Name like "Slack #new-jobs".
Set Destination to Slack.
Paste the Slack webhook URL into URL.
Under Events, check what the channel should hear about. For a jobs channel,
job.publishedalone is usually right; for a hiring-team channel, addapplication.received. Leaving everything unchecked subscribes the channel to all events, which gets noisy fast.Click Add endpoint. A signing secret is shown once; for Slack and Discord destinations you can close this dialog without saving it, because chat messages are formatted posts, not signed JSON.
Confirm it works: click the paper-plane icon (Send test event) on the new endpoint's row. Within a few seconds a test message should appear in your Slack channel, and the delivery shows as Succeeded in the Recent deliveries card.
Post events to a Discord channel
In Discord, open the channel's settings (the gear icon), go to Integrations, then Webhooks, click New Webhook, and copy the webhook URL. It starts with
https://discord.com/api/webhooks/.In easyboard, open Distribution, click Webhooks, then Add endpoint.
Enter a Name like "Discord #job-feed".
Set Destination to Discord.
Paste the Discord webhook URL into URL, pick your Events, and click Add endpoint.
Click Send test event and check the channel for the test message.
easyboard reshapes each event into a readable Discord message; you do not need to configure anything on the Discord side beyond creating the webhook.
Trigger Zapier workflows from board events
Zapier's built-in Webhooks by Zapier app receives easyboard events without any custom integration:
In Zapier, create a new Zap and choose Webhooks by Zapier as the trigger, with the event Catch Hook.
Zapier shows a unique webhook URL. Copy it.
In easyboard, open Distribution, click Webhooks, then Add endpoint.
Set Destination to Generic (signed JSON), paste the Zapier URL, check the events that should fire the Zap, and click Add endpoint.
Back on the endpoint row, click Send test event so Zapier catches a sample payload, then continue building the Zap: Zapier lets you map fields from the payload's
eventanddatainto any of its thousands of connected apps.
From here you can, for example, add every application.received to a Google Sheet, post job.published to social media, or create CRM contacts from employer.created. Every matching event fires your Zap automatically.
Push data from Zapier into your board
The reverse direction goes through your board's REST API rather than webhooks:
Create an API key: in the sidebar, open Distribution, click API, then Create key (see The REST API for the full walkthrough).
In Zapier, add a Webhooks by Zapier action step with the event POST.
Set the URL to your board's API base plus the resource, for example
https://YOUR-BOARD-DOMAIN/api/v1/jobs.Add a header:
Authorizationwith the valueBearerfollowed by a space and your key.Send JSON with at least a
titleand either acompany_nameor anemployer_id; add"status": "published"to publish immediately.
This turns any Zapier trigger (a form submission, a spreadsheet row, an ATS event) into a job posting on your board.
Good to know
Slack, Discord and Zapier endpoints all share the webhooks delivery pipeline: failed sends are retried automatically, everything is visible in the Recent deliveries log with a Redeliver button, and an endpoint that fails 10 deliveries in a row is auto-disabled until you re-save it as active. Details in Webhooks.
One endpoint posts to one channel. Want jobs in one channel and applications in another? Create two endpoints with different event selections.
Deleting the webhook on the Slack or Discord side makes deliveries fail with a 4xx; delete or pause the matching easyboard endpoint too so it does not sit failing.
For notifying your job seekers (rather than your team), use job alerts instead: they email subscribed candidates about matching new jobs.

