← data exports  /  apify actor

Computrabajo Job Alerts: New Jobs to Slack or Webhook

how to get the data with our Apify actor computrabajo-job-alerts

For recruiters and HR analysts: only new, changed or expired Computrabajo job offers in 18 LATAM countries, sent to Slack, Telegram or a webhook each run.

on apify
v0iddo/computrabajo-job-alerts
category
jobs, automation
build
0.1.2, built 2026-11-20
billing
Apify bills it per result; the price for your plan is on the actor's page.

What you get

Every result is one row in the run's dataset. Download it as JSON, CSV, Excel or HTML, or read it through the Apify API.

The main fields of each row:

  • Change (changeType)
  • title
  • company
  • city
  • country
  • Salary (salaryText)
  • Work mode (workMode)
  • Changed (changedFields)
  • First seen (firstSeenAt)
  • Posting (url)

What people use it for

  • Recruiters and staffing agencies: a morning Slack or Telegram message with the new offers of a role, such as contador in Monterrey or vendedor in Bogotá, with company, city, salary and link.
  • HR analysts: which offers of a search changed their salary, title or work mode and which expired, with the old values kept in previous.
  • Claude or any MCP client: ask in plain words, such as "Watch the new contador offers in Monterrey on Computrabajo and send them to my Slack every morning", "Which Computrabajo offers for desarrollador python in Colombia are new since yesterday?" or "Which vendedor offers in Lima on Computrabajo are new, changed or expired since the last check?"
  • n8n and Make: the webhook gets one JSON POST per run with the new and updated offers, ready for an n8n workflow or a Make scenario.

Run it on Apify

  1. Open computrabajo-job-alerts on Apify and sign in, or make an Apify account.
  2. On the Input tab, fill in the fields listed below. The form opens with example values filled in.
  3. Click Start. Rows appear on the Output tab while the run works.
  4. Export the rows as JSON, CSV, Excel, XML or HTML, or read them through the Apify API.
  5. To run it again on a schedule, save the input as a task and add a schedule in the Apify Console.

What you can set

  • Countries (countries): Computrabajo sites to search; each search term runs on each of them. Options: Mexico, Colombia, Argentina, Peru, Chile, Ecuador, Venezuela, Guatemala, Costa Rica, Dominican Republic, Panama, El Salvador, Honduras, Bolivia, Paraguay, Uruguay, Nicaragua, Puerto Rico. Default: ["mx"].
  • Search terms (keywords): Job titles or words such as contador, vendedor or desarrollador python. One search per term, all watched together; leave empty with a city to watch every offer there.
  • City or region (location): Optional city, state or region such as Monterrey, Bogotá, Lima or Nuevo León. Applies to every search term. With Mexico, the default, as the only country, a large city of another country (Bogotá, Lima, Santiago) or a country after a comma (Lima, Peru) searches that country's site.
  • With a salary only (salaryOnly): Only postings that show a salary (not "A convenir"). Default: false.
  • Remote or hybrid only (remoteOnly): Only postings marked remote or hybrid (presencial y remoto). Default: false.
  • Search URLs (searchUrls): Search result pages copied from your browser, for example https://mx.computrabajo.com/trabajo-de-contador-en-monterrey .
  • Watch name (State key) (stateKey): Optional name for this watch, such as contador_monterrey. Runs with the same name share one list of known offers, so you can change the alert addresses or the limits and keep the watch. A new name starts a new watch. Leave it empty and the search fields name the watch.
  • Slack incoming webhook URL (slackWebhookUrl): Optional. The address Slack's Incoming Webhooks app gives you, starting with https://hooks.slack.com/services/. Each run that finds new or updated offers posts one message there.
  • Telegram bot token (telegramBotToken): Optional. The token BotFather gave your bot. With a chat ID, each run that finds new or updated offers sends one message.
  • Telegram chat ID (telegramChatId): The chat, group or channel your bot posts to: a number such as 123456789 or -1001234567890, or @channelname. The bot must be a member of it.
  • Webhook URL (webhookUrl): Optional https address that receives one JSON POST per run with the new and updated offers (title, company, city, salary, link), for n8n, Make, Zapier or your own server.
  • Offers checked per run (maxOffers): The run reads the searches up to this many offers. Offers are reported as expired only after a run that checked every offer, so keep it above the number your searches list. Default: 1000.
  • Include posting details (includeDetails): Read the posting page of each new or updated offer for the contract type, schedule, industry, education, experience, skills and the description. Offers that did not change are never read twice. Default: true.
  • Maximum results (maxItems): The run stops after this many result rows. It also caps what one run can cost. Default: 100.
  • Proxy configuration (proxyConfiguration): Leave as is: the run starts on the cheapest network the site accepts and switches to Apify Proxy automatically when the site blocks it. Pick proxy groups here only to force one specific network.

Example input

This is the input the actor is tested with every day.

example inputjson
{
  "countries": [
    "mx"
  ],
  "keywords": [
    "contador"
  ],
  "location": "Monterrey",
  "includeDetails": true,
  "maxItems": 20
}

Run it from Python

The official apify-client package starts the run, waits for it and reads the rows. It needs your own Apify API token.

needs your own Apify tokenpython
# pip install apify-client
from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")  # your own API token, from the Apify Console
run_input = {
    "countries": ["mx"],
    "keywords": ["contador"],
    "location": "Monterrey",
    "includeDetails": True,
    "maxItems": 20,
}
run = client.actor("v0iddo/computrabajo-job-alerts").call(run_input=run_input)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

Limits

  • Each run compares the offers it finds with the list the last run of the same watch saved, and returns only the changes: NEW for an offer no earlier run returned, UPDATED when its title, company, place, salary or work mode changed (changedFields names them, previous holds the old values), EXPIRED for an offer that is gone from the searches.
  • A watch is the State key, or without one the search fields. The first run of a watch returns the offers it finds as NEW, up to Maximum results; an offer a run found but did not return comes as NEW in a later run, so each change is returned and charged once.
  • Offers are reported as EXPIRED only after a run that checked every offer of the searches: keep Offers checked per run above the number they list. A run in which Computrabajo lists no offer at all reports none as expired. EXPIRED rows carry what the last run saw: title, company, place, salary and link.
  • With a salary only and remote only apply to what the search list shows; an offer that no longer passes them leaves the watch as EXPIRED. Contract type and schedule are on the posting page only, so a change there does not make an offer UPDATED.
  • The list of known offers is one record per watch in the store state-computrabajo-job-alerts in your own Apify account. When it cannot be read, the run stops before reading any page, charges nothing and leaves the record as it was.
  • Alerts: one message per run to each address you give, with the new and updated offers: title, company, city, salary and link, up to 20 in Slack and Telegram and all of them in the webhook JSON. No alert is sent when nothing is new or updated. A delivery that fails is tried once more, never fails the run and is not charged.
  • The webhook, Slack and Telegram token fields are secret input: Apify stores them encrypted, and the log names only Slack, Telegram or the webhook's host.
  • Searches and rows are the same as in our Computrabajo Scraper, with posting details for new and updated offers only. Recruiter names and contact details are not collected; email addresses, phone numbers and handles are removed from the text.
  • Not affiliated with Computrabajo or Redarbor.
  • Only publicly visible data is collected. No login, no paywalled content, no personal contact details.
  • The actor reads only pages that the site's robots.txt leaves open to automated access.
  • Sites change their pages from time to time. The actor is checked automatically and repaired when a check fails.
  • Each run sends one short usage record to the developer: the Actor and run IDs, the number of results, whether the run succeeded (and if not, the kind of error, such as "blocked" or "input problem"), whether the account is on a paid Apify plan, how the run was started (for example from the Console, the API or a schedule) and a one-way fingerprint of the account (a hash, not the account ID), so that repeat runs of one account count once. It contains nothing from your input or results.

Questions

Do I need an account on Computrabajo, cookies or an API key?

No. The actor reads only what every visitor of Computrabajo can see, without logging in. You only need an Apify account to start it.

How many results can one run return?

Up to 10,000 rows per run. Without a limit it stops at 100. Set Maximum results to the number you need; large jobs can also be split into several runs or scheduled.

Why did my run return no results?

The status message of the run says why: nothing matched the input, the input was not a page the actor understands, the page is closed to automated access by robots.txt, or the site refused every network the actor tried. Check the input against the example above and run it again with a small limit.

Can I run it on a schedule?

Yes. Save your input as a task and add a schedule in the Apify Console (daily, hourly or with a cron expression). Each run gets its own dataset, so you keep a history.

Which formats can I export?

JSON, CSV, Excel, XML, HTML table and RSS from the Output tab or the API. Integrations send the rows to Google Sheets, Slack, Make, Zapier, n8n or a webhook.

More

every fact here is read from the actor's public data on Apify, every day; it last changed on