--- title: "Workflows: describe what to watch, and get told when it posts" description: "Workflows turn a sentence into a continuous watch over new job postings. Say what you want to see, in your own words." canonical: https://jobspipe.dev/blog/workflows date_published: 2026-09-05 date_modified: 2026-09-05 author: Dvir Atias --- # Workflows: describe what to watch, and get told when it posts Workflows turn a sentence into a continuous watch over new job postings. Say what you want to see, in your own words. The builder checks the volume, proposes filters plus an AI-judged intent, and you click once. From then on every new match lands in Signals and reaches you by email, Slack or a signed webhook, within hours of the posting going live. This post walks through the builder, the 21 templates, the two modes, and what to connect it to. Most hiring data lands in a dashboard nobody opens. Workflows are the opposite. You describe what you want to watch in one sentence, JobsPipe keeps watching new postings for you, and when a match appears it reaches you where you already work. It is live today for every account at [jobspipe.dev/dashboard/signals](https://jobspipe.dev/dashboard/signals). Workflows · builder Alert me when fintech companies in Germany start hiring for Kubernetes search\_jobsskills kubernetes · industry 64, 65, 66 · in DEchecking volume · volume checked Fintech + Kubernetes hires, Germany Alerts once per company that starts hiring · within hours AI relevance check: _Financial services companies adopting Kubernetes in their own technology infrastructure_ Email · daily digestCreate workflowCreated Watching · new matches land in Signals DevOps System Integration Engineer (all genders) ![](https://www.google.com/s2/favicons?domain=bnpparibas.com&sz=32)BNP Paribas · Germany Today Senior Data Engineer, Banking / Data Analytics ![](https://www.google.com/s2/favicons?domain=s-rating-risikosysteme.de&sz=32)Sparkassen Rating und Risikosysteme · Germany Today Full Stack AI Engineer, Innovation ![](https://www.google.com/s2/favicons?domain=db.com&sz=32)Deutsche Bank · Deutschland Today Email Slack alert.matcheddelivered within hours of the posting going live One run of the builder, start to finish. Every frame is the real product; it loops while it is on screen. ## One sentence in, one workflow out The builder is a chat, and it understands hiring language. “Alert me when fintech companies in Germany start hiring for Kubernetes” becomes a country filter, a skills filter, an industry filter and an intent, without you touching a form. Behind the chat sits a model (Claude Sonnet 4.5 by default, switchable in the header) with three built-in tools: it can search the live index to check volume, it can scan a company’s website to see what technologies it runs, and it can propose a workflow. The flow is deliberately short. It asks at most one clarifying question, and only when the request is too vague to configure. It then runs a single search with its candidate filters to see how much volume you would get, and proposes a card. Nothing is created until you click the button on that card. The builder cannot create a workflow on its own, and it will say so if you ask it to. ![A proposed workflow card: Fintech and Kubernetes hires in Germany, alerts once per company that starts hiring, within hours, with an AI relevance check sentence](https://jobspipe.dev/blog/workflows/proposal.png) The proposal for the first example request. The filters are written back in plain words, and the AI relevance check is the sentence the builder wrote from your intent. ## Two modes: companies and jobs Every workflow runs in one of two modes, and picking the right one is most of the work. - **Companies** fires once per company that starts hiring for what you described. This is the mode for buying signals, target-account lists, competitor tracking and BD leads. A company that opens ten matching roles this week is one alert, not ten. - **Jobs** fires for every matching posting. This is the mode for a recruiter sourcing feed, a job-board inventory webhook, or a personal alert where you want each role. The builder picks the mode from your wording and shows it on the card, so you can change it before anything is created. ## The intent sentence is the precision layer Filters are broad on purpose. Titles and skill slugs catch the candidates; they cannot tell whether a consultancy that mentions Kubernetes is a company adopting Kubernetes. That is what the intent is for. When your request carries meaning beyond the literal filters, the builder writes a one-sentence intent in your own terms, for example “financial services companies adopting Kubernetes in their own technology infrastructure”. Every match is re-judged against that sentence by AI before it alerts you. A plain title feed or a watch on one named company needs no intent, and the builder leaves it empty. ## What the filters can and cannot do Under the hood a workflow is a saved search over the same index as the [hiring signals API](https://jobspipe.dev/hiring-signals-api), so the vocabulary is the same: - Regions become ISO country lists (“DACH”, “Nordics” and “North America” all expand), US states and Canadian provinces become region codes, cities become locations. - Roles become `job_title_or`; technologies and domains become `skills_or` slugs. There is no free-text description filter in workflows, so the skill slug is the technology handle. - Seniority uses five levels, and the builder includes unlabeled postings for non-executive levels, because most ads carry no seniority label at all. - “Direct employers only” sets `employer_type_not` to agencies and brokers. Company-size words map to employee-count bounds. Named accounts go to `company_name_partial_match_or`. - Employment type is applied with unlabeled postings included, since roughly a quarter of postings carry no type. “Remote” is a flag. There are no salary or revenue filters. If you ask for one, the builder says so and configures the closest honest alternative instead of pretending. ## Twenty-one templates when you would rather not type ![The Workflow templates gallery with the categories Sales and lead gen, Recruiting, Competitive intel, Job boards and feeds, Job seekers, and Research](https://jobspipe.dev/blog/workflows/templates.png) Every template opens pre-configured and editable. The footer of each card tells you the mode and the cadence. Templates cover six jobs to be done. Sales and lead gen: companies adopting a technology, target-account hiring watch, ICP hiring surge, new GTM team build-outs, function build-out watch, executive and leadership hires, ATS-customer hiring signal, startup hiring watch. Recruiting: sourcing feed, agency BD leads. Competitive intel: competitor posting tracker, regional expansion watch, hiring-freeze warning, closed-role watch. Job boards and feeds: inventory webhook. Job seekers: personal, remote-only and contract alerts. Research: skill-demand digest, market trend report, salary benchmark alert. ![The New GTM team build-outs template opened as a form: name, country, company size, an exclude-agencies toggle, the AI relevance sentence, an email destination, a daily digest cadence, and a noise preview](https://jobspipe.dev/blog/workflows/template-config.png) A template opened as a form. The noise preview at the bottom tells you what the filters will match before you commit. ## Delivery: email, Slack or a signed webhook Matches land in [Signals](https://jobspipe.dev/dashboard/signals), the same place saved searches from [the original Signals launch](https://jobspipe.dev/blog/introducing-signals) live, and they reach you through one of three destinations: - **Email**, either as each match is found or as a daily digest. - **Slack**, into the channel you pick. - **Webhook**, an HMAC-signed `alert.matched` payload with the same signing scheme as our [job webhooks](https://jobspipe.dev/blog/webhooks-ga-12mo-history), so your pipeline can verify it. “Instant” means within hours of a posting entering the index, not minutes, and the builder says so rather than overpromising. Matches are keyed on the first time a posting entered the corpus, so a reposted or backfilled ad does not fire twice. Evaluating a workflow costs no job credits; you pay only for postings you pull through the API. ## Bring your own tools ![The MCP servers dialog: connect your own tools to the workflow chat, with one server listed and an Add MCP server button](https://jobspipe.dev/blog/workflows/tools.png) The Tools dialog. Any public MCP server you add becomes a tool the builder can call while it configures a watch. The builder is itself an agent, and it accepts tools. Under Tools you can add any public MCP server, and from then on the builder calls it when it helps: pull the account list from your CRM before configuring a target-account watch, or check a company’s stack before settling on a skill filter. Every chat is saved under History, so a watch you refined last week is one click away. If you build agents yourself, the same index is available to them through [our MCP server](https://jobspipe.dev/blog/jobspipe-mcp-server). ## Plans Every plan includes Workflows. Free accounts can run three, delivered by email. Paid accounts run ten, and fifty from 300,000 credits a month, with Slack and webhook destinations from Builder up. If you are on the API already, nothing changes: a workflow is a saved search that runs for you, and the postings it finds are the same records the API returns. Open [Signals](https://jobspipe.dev/dashboard/signals), choose New signal, and describe the thing you keep checking by hand. The builder does the rest. ## Frequently Asked Questions ### What is a JobsPipe Workflow? A Workflow is a continuous watch over new job postings that you set up by describing it in plain words. The builder turns the sentence into filters and an AI-judged intent, checks how much volume the watch would produce, and proposes a card. Clicking the card creates the workflow; from then on every new match lands in Signals and reaches you by email, Slack or webhook. ### How is a Workflow different from a Signal? A Signal is a saved search with alerts. A Workflow is the chat-driven way to create one: you describe what to watch, the builder configures the search, picks the mode (one alert per company that starts hiring, or every matching posting) and writes the intent sentence that AI uses to re-judge each match. Workflows run continuously and their matches appear in Signals. ### How quickly does a Workflow alert fire? Within hours of a posting entering the index, not minutes. Matches are keyed on the first time a posting entered the corpus, so a reposted or backfilled ad does not fire twice. Email can be sent per match or as a daily digest. ### Where can Workflow alerts be delivered? Email, as each match is found or as a daily digest; Slack, into a channel you pick; or a webhook that receives an HMAC-signed alert.matched payload you can verify. Slack and webhook destinations are available from the Builder package up. ### How many Workflows can I run, and what do they cost? Free accounts can run three, delivered by email. Paid accounts run ten, and fifty from 300,000 credits a month. Evaluating a workflow consumes no job credits; you pay only for postings you pull through the API. ### Can the Workflow builder use my own tools? Yes. Under Tools you can connect any public MCP server, and the builder calls it when it helps, for example to pull an account list from your CRM before configuring a target-account watch. Chats are saved under History. Related ## Keep reading - [Product · Sep 23, 2026Agentic search: describe the job in a sentence, get the postings that fit](https://jobspipe.dev/blog/agentic-search) - [Product · Oct 11, 2026YC startups hiring now: the fastest-hiring startups in every YC batch](https://jobspipe.dev/blog/yc-startups-hiring) - [Product · Sep 18, 2026The highest-paying AI jobs in September 2026](https://jobspipe.dev/blog/highest-paying-ai-jobs-september-2026) - [Product · Aug 29, 2026JobsPipe for Slack: search live job postings without leaving the channel](https://jobspipe.dev/blog/jobspipe-for-slack) - [Product · Aug 8, 2026Introducing Signals: stop checking whether a company started hiring](https://jobspipe.dev/blog/introducing-signals) ## Further reading - [JobsPipe Pricing](https://jobspipe.dev/pricing) --- Try it with no key: `curl -d '{"limit":3}' https://api.jobspipe.dev/v1/sandbox/jobs/search`. AI agents: the full machine-readable index of this site is https://jobspipe.dev/llms.txt?src=md-twin - API quickstart, MCP server, pricing. Free key (1,000 jobs to start): https://jobspipe.dev/signup