Resources · Zapier integration

Madgex Job Board Zapier integrationAutomate Madgex Job Board with Zapier.

The Madgex Job Board Zapier integration has 13 triggers, 1 action and no search. Every trigger is instant: jobs, job alerts, recruiters, profiles, users and content reports all reach Zapier as they happen. The single action updates a user's marketing preferences.

See the 14 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Madgex Job Board Zapier integration is for

It pushes what happens on your Madgex job board out to the rest of your tools, the moment it happens. Madgex is job board software. On Zapier it is mostly a source of events: thirteen instant triggers covering jobs, alerts, recruiters, profiles and users, plus one action that writes back a user's marketing preferences.

A live feed of new jobs. Job Published fires when a job moves from draft to live, so your team chat or a shared sheet can list every new posting without anyone checking the board.

Recruiter accounts that stay in sync. Recruiter Published, Recruiter Status Changed and Recruiter Updated let another tool follow each recruiter record as it goes live, changes status or gets edited.

Moderation that does not wait. Content Report Created fires on each new content report, so whoever reviews reports hears about it straight away instead of finding it later.

What the integration does not do: there is no search and only one action. A Zap cannot post a job, create a recruiter, edit a profile or delete a user; it can only update a user's marketing preferences from their email address. Everything else on Madgex is read-only from Zapier's side. To compare this with other platforms, read the n8n vs Zapier comparison before you settle on one.

Vocabulary

Zapier vocabulary in one minute

Seven words keep coming back on this page. Here they are in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it. Madgex offers thirteen of them.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you in an app.
Task
The unit Zapier bills: one action your Zap completes successfully. The count on your plan is a count of those.
Instant trigger
A trigger the app reports itself: it calls Zapier the moment the event happens, so nothing waits for a scheduled check.
Polling trigger
A trigger Zapier checks on a timer, asking the app for new items at a fixed interval and keeping the unseen ones.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Cost

What a Madgex Job Board Zap really costs

Madgex Job Board is not a premium app, so it works on the free plan. You pay in tasks, and only for actions that succeed.

  • Triggers (13)all instant, never counted
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Premium appno, works on the free plan

The trigger never costs a task, however many jobs, alerts or users Madgex reports. Each successful action is one task: a message posted after Job Published is one, and so is each Update User Marketing Preferences that goes through. A failed action is not counted. The free plan gives 100 tasks a month and two-step Zaps: one trigger and one action. A filter or a second action makes the Zap multi-step, which needs a paid plan. The grid below sets how often Zapier checks a polling trigger on each plan; it does not apply to Madgex, whose thirteen triggers are all instant.

Connect

Connect Madgex Job Board to Zapier in 3 steps

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. In the dialog that opens, type Madgex Job Board in the search box and pick it from the results.

  2. 02

    Sign in to Madgex

    Click Add connection. A tab opens on Madgex: sign in with the account of the job board you want the Zap to follow. You need that account before the connection can be made.

  3. 03

    Grant access

    Approve the access Zapier asks for. The connection then shows on the Apps page, and every Zap step that uses Madgex reuses it. Anything you do not own needs read or write access.

First Zap

Your first Zap: new live jobs posted to your team chat

GoalEach job that goes live on your Madgex board posts a message to your team chat, but only for the jobs your filter lets through.

  1. 01

    Pick the trigger

    Create a Zap, choose Madgex Job Board and the Job Published event. It fires when a job goes from not live, a draft for example, to live.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent published jobs of the connected board. Pick a real one so the rest of the mapping uses actual job data.

  3. 03

    Add the filter

    From the plus icon, add Filter and fill its three boxes: the field to look at, the rule and the value. A text rule only works on text, so match the rule to the field.

  4. 04

    Add the chat message

    Add your team chat with its send-message action, then write the message with fields from the job. Test the step and check how it reads in the channel.

  5. 05

    Publish

    Click Publish to switch the Zap on. The filter makes it multi-step, so a paid plan is needed; on the free plan, keep only the trigger and the action.

Triggers

Madgex Job Board triggers

13 events start a Zap when something happens in Madgex Job Board, and 13 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Content Report Created

Instant trigger

In Zapier“Triggers when a new content report is made.”

Fires each time someone files a new content report on your board. Whatever the report carries is handed to the next steps, so it can reach your team instead of waiting in the back office.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
reports should land in a shared inbox or a chat channel the moment they are filed.
Watch out
reports filed before the Zap was switched on are never sent.
2

Job Alert Created

Instant trigger

In Zapier“Triggers when a new job alert is created.”

Reacts when a user sets up a new job alert on the board. The alert becomes data for the steps after it, which is a simple way to see what people are asking to be notified about without opening Madgex.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
new alerts should be logged in a spreadsheet so demand for each kind of job can be read in one place.
Watch out
an edited alert does not fire this trigger; it fires Job Alert Updated.
3

Job Alert Updated

Instant trigger

In Zapier“Triggers when an existing job alert is updated.”

Starts a Zap when an existing job alert is changed. It is the companion of Job Alert Created and keeps any copy of the alert outside Madgex in line with what the user now wants.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
alerts are already copied to a sheet and the row should follow each edit.
Watch out
with no search on Madgex, the matching row has to be found by the other app, through its own search step if it has one.
4

Job Published

Instant trigger

In Zapier“Triggers when a job goes from not live (eg. draft) to live.”

Goes off when a job moves from not live, a draft for example, to live on the board. It is the clearest signal that a posting can now be seen, which makes it the natural start for announcing new jobs elsewhere.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
every new live job should appear in your team chat or a shared list.
Watch out
saving a draft does not fire it; only the switch to live does.
5

Job Updated

Instant trigger

In Zapier“Triggers when a live job is edited and being marked as archived.”

Runs when a live job is edited and being marked as archived, according to the official wording. Use it to follow a posting after it went live, rather than for its first publication.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a list of open jobs kept outside Madgex should drop or flag a posting once it gets archived.
Watch out
the official description ties the edit to archiving, so test it on a real job before relying on it for every small change.
6

Profile Created

Instant trigger

In Zapier“Triggers when a new user profile is created.”

Fires whenever a new user profile appears on the board. The profile details flow into the following steps, ready to be logged or passed on to another tool your team works in.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
each new profile should create a row in a sheet that your team reviews.
Watch out
a profile and a user are separate events on Madgex; User Created covers the account itself.
7

Profile Updated

Instant trigger

In Zapier“Triggers when an existing user profile is updated.”

Kicks in when an existing user profile is edited. It keeps whatever copy of that profile lives outside Madgex from going stale, since the change reaches Zapier as soon as the user saves it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
profiles are mirrored in another tool and edits should follow there too.
Watch out
busy profiles can fire this often, and every action that follows costs one task each time.
8

Recruiter Published

Instant trigger

In Zapier“Triggers when Recruiter record is published to active/live.”

Triggers when a recruiter record is published and becomes active or live. This is the moment a recruiter really appears on the board, so it suits anything that should happen once that account is up and running.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
your team should hear about it as soon as a recruiter goes live.
Watch out
a move from non-active to active fires this trigger, not Recruiter Status Changed.
9

Recruiter Status Changed

Instant trigger

In Zapier“Triggers when Recruiter status has changed (note: if status changes from non-active to active Recruiter Published trigger is fired).”

Tells the Zap that a recruiter's status has changed. The official note adds one exception: going from non-active to active fires Recruiter Published instead, so this trigger covers the other transitions.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a recruiter record in another tool should show the same status as on Madgex.
Watch out
activations never come through here, so a Zap built only on this trigger will not see a recruiter going live.
10

Recruiter Updated

Instant trigger

In Zapier“Triggers when Recruiter properties have been updated.”

Responds when the properties of a recruiter record are edited. Where Recruiter Status Changed watches the status alone, this one follows the rest of the record's details.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
recruiter details are kept in a spreadsheet and should not drift from the board.
Watch out
the official description does not say which properties count, so look at what the test brings back before mapping anything.
11

User Created

Instant trigger

In Zapier“Triggers when a new user is created.”

Fires when a new user account is created on the board. It is the first point at which someone exists on Madgex, which makes it the start for welcoming them or logging the sign-up elsewhere.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
each sign-up should be added to a mailing list or a sheet without anyone exporting users.
Watch out
users created before the Zap was published are not sent; moving them is a separate job.
12

User Deleted

Instant trigger

In Zapier“Triggers when a user is deleted.”

Comes through when a user is removed from the board. It lets other tools that hold a copy of that user hear about the deletion and act on it, instead of keeping an account that no longer exists.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a deleted Madgex user should also be removed or flagged in your mailing tool.
Watch out
after deletion the user is gone on Madgex, so do not plan a later Madgex step on that user.
13

User Updated

Instant trigger

In Zapier“Triggers when a user is modified.”

Starts the Zap whenever a user is modified. It is the broadest of the user triggers and catches edits to the account rather than to the profile.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
user details copied to another tool should change there as soon as they change on the board.
Watch out
before you pair it with Update User Marketing Preferences, test whether a preference change counts as a user edit; nothing documents it, and if it does, the Zap would restart itself.
Actions

Madgex Job Board actions

Madgex Job Board gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Update User Marketing Preferences

Action

In Zapier“Updates the indicated User Marketing Preferences with the indicated values.”

Changes the marketing preferences of a Madgex user, found by email address, to the values you set. You name each preference and give it its new value.

When to use it
someone opts in or out in another tool, a form for example, and the board should reflect that choice.
Watch out
both fields are required, and the email must match an existing user on the board exactly.
When it breaks

When a Madgex Job Board Zap breaks

Zapier links no help article to Madgex Job Board and publishes no rate limit for it. What can go wrong comes from the way every Zap works.

Four cases are worth planning for before you publish. If a Zap already misbehaves, the Zapier troubleshooting guide helps you trace the cause.

  • Past jobs and users are not picked up

    A Zap reacts only to what happens after it is switched on. Jobs, alerts and users that existed before are ignored; moving them is a separate job.

  • When a Zap could restart itself

    A Zap that writes where its own trigger watches restarts itself and burns tasks. If you pair User Updated with the preferences action, test it on one user first.

  • A bulk import is held back

    When a trigger suddenly sends a huge batch, after an import or a migration, Zapier's flood protection can hold those runs back.

  • The user's email does not match

    Update User Marketing Preferences finds the user by email. If the address is empty or differs from the one on the board, the step fails.
Need help

Need help automating Madgex Job Board with Zapier?

A person reads every message.

FAQ

Madgex Job Board Zapier integration: FAQ

01Is the Madgex Job Board Zapier integration free?
Yes, as long as the Zap has two steps. Madgex Job Board is not a premium app, so the free plan can use it, with 100 tasks a month and Zaps made of one trigger and one action. Job Published followed by a chat message fits that shape. Add a filter, for example to keep only some jobs, or a second action, and the Zap becomes multi-step, which needs a paid plan.
02How many Zapier tasks does a Madgex Job Board Zap use?
One task per action that succeeds, and nothing for the trigger. A Zap that posts a chat message for each live job uses one task per job. If it also adds a row to a sheet, each job costs two. A failed action is not counted. Madgex can report as many new jobs, alerts or users as it likes; the triggers themselves never take a task from your plan. Only completed work is billed.
03Is Madgex Job Board on Zapier real time?
Yes, for all thirteen triggers. Every one of them is instant: Madgex tells Zapier the moment a job goes live, an alert changes or a user is created, and the Zap starts straight away whatever your plan. The polling grid, 15 minutes on Free down to one minute on Team and Enterprise, does not apply to any of them. In the editor, a Zap built on one shows a lightning bolt.
04What does it take to connect Madgex Job Board to Zapier?
A Madgex account for the board, plus read or write access to anything you do not own and want the Zap to touch. In Zapier you open the Apps page, click + Add connection, search for Madgex Job Board, sign in in the tab that opens and grant access. The connection is then reused by every Zap on that board. Use an account that can see the jobs and users the Zap should follow.
05Why does Recruiter Status Changed miss some changes?
Because one transition belongs to another trigger. According to the official description, when a recruiter goes from non-active to active, Madgex fires Recruiter Published, not Recruiter Status Changed. A Zap built only on the status trigger therefore never sees activations. Activations are carried by Recruiter Published, so keep that in mind when you choose which trigger starts your Zap. Test on a real recruiter record and look at what arrives before relying on it.
06What if the Madgex Job Board operation needed is not on Zapier?
Then the integration cannot do it. The visible menu is thirteen triggers and one action, Update User Marketing Preferences, with no search. Posting a job, creating a recruiter, editing a profile or deleting a user from a Zap are not in the editor. The options are to keep those steps in Madgex, to rethink the flow so Madgex only sends events out, or to check another automation platform. There is no search either, so a Zap cannot look up a job or a user.
07Zapier, Make or n8n for Madgex Job Board?
Decide on criteria, not on a ranking. On Zapier, Madgex Job Board gives thirteen instant triggers that work on the free plan in two-step Zaps, which suits sending board events to other tools. If you need to write much back into Madgex, the single action is the limit. Compare which Madgex operations each platform exposes, how each one bills, and who on your side will maintain the flow, then choose on that basis.
Same platform

Other docs you might need on this stack.

Browse all integrations