The moment it happens

Get a short summary of each new Workable applicant

Every new application arrives in your inbox with a few lines on the candidate's experience and skills.

Runs: The moment it happens
Apps: Workable
AI: Yes, uses the built-in AI allowance
Access: r_candidates

Send this to your assistant

Create a ClickRuntime automation: when someone applies to our Customer Success Manager job in Workable, summarise their resume in 3-4 bullets covering years of experience, recent roles and relevant skills, and email it to me.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

Recruiters at a growing company can get 60 applications on a single job posting within two days. Reading each resume in full to decide whether to call is slow, so strong candidates wait in the queue behind weak ones, and the hiring manager hears about a good applicant only after a competitor has already made an offer.

The moment a candidate applies in Workable, the event reaches ClickRuntime, the candidate's details are fetched, and the built-in AI writes a short summary covering experience, skills and anything that looks relevant to the role. That summary is emailed to the hiring contact right away.

It works best for roles with high volume, or where the person reviewing applications is not a full-time recruiter, such as a founder or team lead. The summary sits in the hiring contact's inbox minutes after the candidate applies.

What you get out of it

Good candidates are spotted sooner
A short summary within moments of applying lets you call a promising person on the same day, before they accept another offer from a faster employer. Speed in the first 48 hours is often what separates the offer you win from the one you lose.
Hiring managers read less, decide more
A paragraph on experience and skills is quicker to scan than a full resume, which helps busy managers give every applicant a fair first look. That is especially useful for founders and team leads who review applicants beside their regular job.
Screening feels more consistent
Each applicant gets a summary in the same structure, so comparing three candidates for one role is easier than comparing three differently formatted documents. A common format reduces the chance that a strong candidate is overlooked because their resume looked different.
Applicant details stay in Workable
The summary is an email aid. The candidate record, resume and any notes remain in Workable, so your system of record is not duplicated or altered. Keeping a single source of truth avoids confusing duplicate notes across two systems.
Quick triage on busy postings
When a job ad is shared widely and applications spike, the summaries keep the review queue manageable instead of letting it grow for a week unseen. That keeps review time under control without ignoring anyone who applies.

How it works

What happens, step by step

When someone applies through Workable, Workable tells ClickRuntime straight away.
ClickRuntime fetches the candidate's full profile and resume details.
AI writes a few lines on their experience, most recent role and strongest skills.
You get an email with that summary and the job they applied for.

Before it runs live

Connect Workable
Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens

Get a short summary of each new Workable applicantjust nowSucceeded

Email · New CSM applicant: Nadia Karim• 6 years in B2B SaaS customer success • Most recently Senior CSM at Acme Analytics (2022–now) • Strong on onboarding and renewals

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Act only on the items that match your own rules, and skip the rest
Change what the AI looks for, or how it writes the result
Add another app, for example also send it to Slack
Combine it with other Workable steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

ai_screening_summary_of_new_candidates.pyexample

from clickruntime import on_event, credentials, http, ai, notify

SUBDOMAIN = "northwind"
JOB_TITLE = "Customer Success Manager"

@on_event
def handle(event):
    payload = event.json or {}
    data = payload.get("data", {})
    if payload.get("event_type") != "candidate_created" or (data.get("job") or {}).get("title") != JOB_TITLE:
        return {"sent": False}
    c = http.get(f"https://{SUBDOMAIN}.workable.com/spi/v3/candidates/{data['id']}",
                 headers={"Authorization": f"Bearer {credentials.secret('WORKABLE_API_TOKEN')}"}).json()["candidate"]
    roles = "\n".join(f"{e.get('title')} at {e.get('company')} ({e.get('start_date')} - {e.get('end_date') or 'now'})"
                      for e in c.get("experience_entries", []))
    skills = ", ".join(s["name"] for s in c.get("skills", []))
    summary = ai.generate(f"Summary: {c.get('summary') or ''}\nExperience:\n{roles}\nSkills: {skills}"[:6000],
                          system="Write 3-4 bullets: years of experience, recent roles, skills relevant to customer success.",
                          max_output_tokens=250).text
    notify.email_me(f"New CSM applicant: {c['name']}", f"{summary}\n\n{c.get('profile_url', '')}")
    return {"sent": True}

FAQ

Common questions

Does the AI decide who gets rejected?

No. It writes a summary and nothing else. It does not move candidates between stages or reject anyone, so the decision stays with the recruiter. Treat the summary as a reading aid, and check the full profile before drawing conclusions.

What candidate information is included?

The summary draws on the profile data Workable returns for the candidate, such as work history, education, skills and any answers to application questions, depending on what the applicant supplied and what your account exposes.

Is it fair to use AI on applications?

Hiring rules differ by country and region, and some places require notice or limit automated assessment. Because this only summarises and does not score or reject, it is lower risk, but check local requirements with your legal advisor.

What permissions does it need?

r_candidates. Nothing else in your accounts is used.

Does it need AI?

Yes. It uses ClickRuntime's built-in AI, so you don't need an OpenAI or Anthropic key. Every plan includes a monthly AI allowance.

How many runs does it use?

One run for each event the app sends.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

The moment it happens