Jobs Watchlist to Airtable
Jobs Watchlist to Airtable
Apps used in template
About
Keep an Airtable table in sync with new job postings from any company watchlist, straight from the companies' own ATS.
HOW IT WORKS
- HTTP - Make a request runs the Apify actor make_no_mistakes/multi-ats-job-board-api and returns the jobs as JSON.
- Iterator splits the returned array so each job is handled on its own.
- HTTP - Make a request upserts one record per job into Airtable (PATCH with performUpsert), so re-runs update rows instead of duplicating them.
WHAT YOU NEED
- Apify API token: get it at https://console.apify.com/settings/integrations (Personal API tokens). Paste it into the Authorization header of module 1, keeping the "Bearer " prefix.
- Airtable personal access token: create one at https://airtable.com/create/tokens with the data.records:write scope on your base. Paste it into the Authorization header of module 3, keeping the "Bearer " prefix.
- Your Airtable base ID and table name, set in module 3's URL in place of REPLACE_WITH_BASE_ID and REPLACE_WITH_TABLE_NAME.
- An Airtable table with columns matching the mapped fields: company, ats, job_id, title, department, location_raw, is_remote, employment_type, salary_min, salary_max, salary_currency, posted_at, apply_url.
OPTIONAL
- Edit "companies" in module 1's body to your own watchlist and "postedWithinDays" for the look-back window.
- Set the scenario schedule to run once a day.
Actor pricing: $0.005 per run plus $0.004 per job returned.
Trusted by thousands of fast-scaling organizations around the globe
Similar templates for inspiration
Looking to get more out of your apps? With Make, you can visually integrate any app into any workflow to save time and resources - no coding required. Try any of these templates in just a few clicks.
Create your own workflow
Create custom workflows by choosing triggers, actions, and searches. A trigger is an event that launches the workflow, an action is the event.
Combines multiple bundles into a single array. This is the opposite of an Iterator.
Downloads a file from a given URL.
Splits an array into individual bundles to process one at a time. This is the opposite of an Array aggregator.
Sends an HTTP(S) request to a specified URL that requires Basic Auth authorization and processes the response.
Sends an HTTPS request to a specified URL that requires Client Certificate Auth authorization and processes the response.
Sends an HTTP(S) request to a specified URL and processes the response.
Sends an HTTPS request to a specified URL that requires API Key Auth authorization and processes the response.
Sends an HTTP(S) request to a specified URL that requires OAuth 2.0 authorization and processes the response.
Runs the next modules a set number of times and returns an incremental number.
FAQ
Start by registering for Make. As a new Make user, you’ll automatically be assigned a free account. Once your account is set up, you can start creating your first scenarios. We recommend starting with our step-by-step video tutorial.
A scenario represents a workflow or a project of your own creation, and it is made up of a series of modules that automate apps and services. Creating a scenario allows you to transfer and transform data between apps and services via these modules to automate anything and improve the way you work.
Modules are the main building blocks of automation in Make. Modules represent actions that Make performs with an app, like creating, updating, or deleting data.
Mapping links the modules in your scenario. When you map an item, you connect the data retrieved by one module to another module to perform the desired action. For example, you can map email addresses and subject lines to create a spreadsheet using this data.
How it works
Traditional no-code iPaaS platforms are linear and non-intuitive. Make allows you to visually create, build, and automate without limits.










