Beta

Use Notion with an AI Browser for Candidate Sourcing

Run candidate sourcing in Strawberry using Notion as one of the inputs. Specific surfaces, example prompt, real output, and tradeoffs vs alternatives.

Diagram of Strawberry AI browser workflow using Notion for candidate sourcing

If you use Notion and you regularly need to source candidates, the bottleneck is usually the same: Notion holds part of the context, but candidate sourcing also needs signals that live outside it - on the public web, in LinkedIn, in news, in other connected apps. Strawberry is built to combine the Notion context with the rest of the browser, and run the full workflow as a companion you can re-trigger every week.

This page describes specifically how Strawberry handles candidate sourcing when Notion is one of the inputs. It names the Notion surfaces involved, the signals the workflow actually needs, an example prompt you can paste, and what a good output looks like.

The job a recruiter, founder hiring, hiring manager is trying to do

The goal of candidate sourcing is to build a shortlist of 10-30 candidates who match the role and have at least one signal of openness. The success metric is concrete: 30% reply rate to first outreach, 5+ first-call conversions per 30 sourced. That definition matters because it shapes what Notion needs to contribute to the workflow.

What signals candidate sourcing actually needs

For each signal below, here is whether Notion can contribute directly or whether Strawberry has to find it via the browser:

  • Current role and tenure - Notion does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
  • Recent role changes (often visible on LinkedIn) - Notion does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
  • GitHub or content output for technical roles - Notion does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
  • Company stage match (someone leaving a Series B is more likely to talk to a seed-stage co) - Notion does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
  • Geo match for hybrid roles - Notion does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
  • Openness signals (LinkedIn open-to-work, recent comments about job search) - Notion does not contain this directly. Strawberry uses the browser plus public sources to fetch it.

What Strawberry can do inside Notion

Strawberry can query a Notion database, summarize a page, and append structured notes - ideal for research compendiums, project trackers, and team wikis.

Notion surfaces Strawberry uses for this workflow: pages, databases, blocks, filters, views.

How Strawberry runs candidate sourcing with Notion

  1. Strawberry opens the Notion pages that contains the relevant context.
  2. The companion pulls related context from Notion (databases, history, attached files) where it exists.
  3. For the parts Notion does not store, Strawberry uses the browser - web search, LinkedIn, news, the prospect's website.
  4. Strawberry synthesises the output in the shape this workflow needs: A shortlist with one row per candidate.
  5. A human reviews before any external action (send, update, post). Then the approved output is saved back to Notion or your system of record.

Example Strawberry prompt

Paste this in a new Strawberry chat with Notion connected. Adjust the specifics to your actual ICP, role, or topic.

Read this Notion pages and any linked context.
Then run a full candidate sourcing workflow on it. Use the browser to fill any gaps not in Notion.
Return the output in the shape we use for candidate sourcing: A shortlist with one row per candidate: name, current role, target role fit (1-5), one personalised opening line, contact link.
Do not send anything externally. Save the draft to me to review.

What a good candidate sourcing output looks like

Here is what a finished output for candidate sourcing should look like in practice. The specifics will change for your use case, but the shape should look similar:

  • Role: Founding Engineer (Stockholm or remote EU)
  • Candidate: Marek Novak - Senior Engineer @ Klarna, 4 years
  • Fit: 5/5 (worked on payment systems, contributed to Rust open source, recent talk on type-safe APIs)
  • Opening line: noticed his RustConf talk on type-safe API contracts and our backend lead's tweet about Marek's library
  • Contact: LinkedIn DM + GitHub email

Why Notion for this, and where to use a different tool

Notion is strong for this workflow because Strawberry can query a Notion database, summarize a page, and append structured notes - ideal for research compendiums, project trackers, and team wikis.

Where Notion falls short Notion's block-based API doesn't support all formatting; relations and rollups can be brittle through API.

Consider also the rest of your stack for the parts Notion doesn't cover.

Common mistakes when running candidate sourcing

  • Spray-and-pray DMs that mention nothing specific
  • Missing the obvious signals (someone just posted 'thinking about a change')
  • No quality bar - putting 200 names on the list to look productive

Connecting Notion to Strawberry

Notion OAuth - workspace-scoped. Once connected, the companion can read the surfaces above without re-authenticating, and any write action still requires explicit human approval the first time the workflow runs.

Caveats

Do not let any AI agent send emails, update CRM records, or change shared systems without a clear approval step. Strawberry is strongest when the workflow combines browser context with connected-app context and a human review for sensitive actions.

How Notion + Strawberry runs candidate sourcing

1 Notion

Read

Open the relevant Notion pages; pull related context.

2 Browser

Augment

Use the browser, LinkedIn, news, and other connected apps for signals outside the CRM/tool.

3 Output

Compose

Synthesise into the candidate sourcing shape: A shortlist with one row per candidate.

4 Human

Approve

Human reviews before any external action; approved output is saved back.

FAQ - Notion + AI browser for candidate sourcing

Can Strawberry do candidate sourcing entirely inside Notion?

No, and that is the point. candidate sourcing needs signals Notion does not store - public web, LinkedIn, news, other apps. Strawberry combines Notion with the browser, which is where the real value comes from.

Does Notion need to be the primary CRM or system of record?

Not necessarily. Notion can be one input among several. Strawberry can read it as context even if your primary system of record is somewhere else.

What permissions do I need on Notion?

Read access to the surfaces you want Strawberry to use (pages, databases, blocks). Write permissions are only needed if you want Strawberry to update Notion after a human approves the change. Notion OAuth - workspace-scoped.

What is the realistic success metric for candidate sourcing?

30% reply rate to first outreach, 5+ first-call conversions per 30 sourced - that is the target Strawberry helps you hit, not the only thing it measures.

What is the biggest mistake to avoid?

Spray-and-pray DMs that mention nothing specific.

Run candidate sourcing in 10 minutes with Strawberry and Notion

  1. Open Notion

    Connect Notion so Strawberry can read pages, databases, blocks and combine them with the rest of the brief. Pin the specific records or views you want to start from so the agent doesn't drift.

  2. Tell Strawberry the brief

    Drop the prompt below. Replace the placeholder with the actual recruiter, founder hiring, hiring manager target - one name, one URL, or one Notion reference is enough. Keep the goal explicit: build a shortlist of 10-30 candidates who match the role and have at least one signal of openness.

  3. Let it gather signals

    Strawberry pulls current role and tenure and recent role changes (often visible on LinkedIn), then layers public web sources in parallel. You should see citations next to each fact - that is the audit trail. Watch the Notion side: Notion's block-based API doesn't support all formatting; relations and rollups can be brittle through API

  4. Review before write-back

    Output lands in the shape you asked for: A shortlist with one row per candidate: name, current role, target role fit (1-5), one personalised opening line, contact link. Read it once. Fix anything off. The success metric is 30% reply rate to first outreach, 5+ first-call conversions per 30 sourced - if the draft doesn't hit that bar, send it back with a one-line correction.

  5. Save it as a routine

    If you'll source candidates again next week, click Save as routine. Pick a cadence (daily, weekly, on-trigger). Strawberry re-runs the whole flow on schedule and pings you when the new output is ready.

Paste-ready prompt for candidate sourcing with Notion

You are helping me source candidates. Use Notion as one input and the public web for the rest.

Target: [paste one recruiter, founder hiring, hiring manager target here - a Notion reference, a name + company, or a URL]

Goal: build a shortlist of 10-30 candidates who match the role and have at least one signal of openness.

Signals to gather:
- current role and tenure
- recent role changes (often visible on LinkedIn)
- GitHub or content output for technical roles
- company stage match (someone leaving a Series B is more likely to talk to a seed-stage co)
- geo match for hybrid roles
- openness signals (LinkedIn open-to-work, recent comments about job search)

Output shape: A shortlist with one row per candidate: name, current role, target role fit (1-5), one personalised opening line, contact link

Rules:
- Cite every fact with a link or a Notion reference. If you cannot find a signal, say so explicitly rather than guessing.
- Do not invent specifics. Use real, dated signals from the last 90 days where possible.
- If a fact would change the outcome and is missing, pause and ask me before writing the final output.

When the output is ready, surface it in this chat. Do not write back to Notion or send anything externally until I approve.

Paste this into Strawberry's chat field. Replace the target placeholder before running.

When Notion + Strawberry is NOT the right fit for candidate sourcing

Skip this setup if any of the following is true:

  • You don't actually need Notion signals. If everything you need lives on the public web, drop the Notion step and let Strawberry run on URLs alone - it's faster.
  • A known Notion constraint blocks the speed gain: Notion's block-based API doesn't support all formatting; relations and rollups can be brittle through API
  • The buyer (recruiter, founder hiring, hiring manager) doesn't own the decision. If the brief gets handed to someone who'll redo the research, the audit-trail-in-Strawberry advantage is wasted.

3 mistakes that kill this workflow

  1. spray-and-pray DMs that mention nothing specific. Notion is one input. Strawberry's edge is combining it with everything else. Stop at Notion-only signals and you'd have been faster with native Notion reports.
  2. missing the obvious signals (someone just posted 'thinking about a change'). Pre-check Notion for a recent touch or duplicate before Strawberry acts on the output. A duplicate hit burns the relationship.
  3. no quality bar - putting 200 names on the list to look productive. Strawberry is built so a human reviews before any external action. Skipping that review to save time is how you ship a wrong fact to a real person.

Honest tradeoff vs alternatives

You could source candidates inside Notion alone using its native features, or with a dedicated candidate sourcing tool. Notion alone gives you tighter data fidelity but misses every signal that lives off-platform. A specialised candidate sourcing tool gives you better dashboards but its scope ends where its integrations end, and most of the real signal still lives on the open web.

Strawberry's edge with Notion: Strawberry can query a Notion database, summarize a page, and append structured notes - ideal for research compendiums, project trackers, and team wikis The price you pay: an agent run takes 30-90 seconds; a native Notion action loads in 2. For a one-off question you already know the answer to, use Notion directly. For an output you need every week and want to systematise, this is where Strawberry pays off.

Download