HR & RECRUITING

Create Asana intake tasks for each new Indeed applicant

Turns every new Indeed applicant into a structured Asana task in the recruiting project, pre-filled with resume summary and assigned to the right recruiter by role.

CategoryHR & Recruiting
Enginesim
Difficultybeginner
Triggerschedule
Steps4
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSchedule lists new Indeed applicants
  • ActionFetch resume and summarize highlights with OpenAIOpenAI
  • LogicMap job to owning recruiter and project section
  • OutputCreate assigned Asana intake task with summary and due dateAsanaAsana

What it does

This workflow gives every Indeed applicant a home in your recruiting board. On a schedule it pulls new applicants, summarizes each resume into key highlights with AI, and creates an Asana task in the right project section assigned to the recruiter who owns that req, so nobody falls through the cracks.

When to use it

Use it when your team runs hiring out of Asana and wants applicants to show up as actionable, owned tasks instead of buried emails. Ideal for teams that already track screening, interviews, and offers as task stages.

How it works

  1. 1A schedule fires and lists new applicants across your matched Indeed jobs.
  2. 2The workflow fetches each resume and an OpenAI step writes a tight three-line summary of experience and fit.
  3. 3A logic step maps the job to its owning recruiter and Asana project section.
  4. 4An Asana task is created with the candidate name, resume summary, and a link, assigned to that recruiter with a screening due date.
  5. 5The task lands in the New Applicants section ready for triage.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect OpenAIModels, embeddings, files.
  2. 2
    Connect AsanaTasks, projects, milestones — everywhere.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.