Use the Smart actions trigger to let Co-pilot handle specific tasks automatically, helping you spend less time on manual work and more time on what matters. Simply describe what you want Co-pilot to do in plain language and choose the action it should perform.

Smart actions let Co-pilot perform a task automatically when a candidate reaches a specific job stage. You can use them to add comments, fill custom fields, add or remove candidate tags, or create to-dos.

Co-pilot uses information available to the hiring team, such as the candidate’s application, resume, answers, and comments, to determine what action to take. Comments, questions, and custom fields set as Private are excluded.

Depending on the action, Co-pilot may complete the task with partial information or require specific information or conditions to be met.

Describe the task you want Co-pilot to perform in plain language (max. 2000 characters). Be specific about what information to look for, which criteria to use, and what the expected result should be.

Verify your prompt to check that Co-pilot understands the requested action.

You will need to verify again whenever you change the prompt, destination field, or selected tags.

Each task performs one action type, but you can add multiple tasks (triggers) per stage. Smart actions cannot send messages to candidates, move or reject applications, or combine multiple actions in a single task.

The following actions are supported when setting up the trigger:

Use this action to add a comment to the candidate's job application based on the information available to Co-pilot.

Information

If information is missing, Co-pilot explains what is missing and which sources it checked. If it can answer part of the request, it adds a partial answer. If you don't specify what information to include, it adds one short paragraph.

Comment formatting

Comments support paragraphs, bold and italic text, links, and lists. Headings, images, code blocks, tables, and @mentions are not supported. Adding a comment does not trigger notifications.

Use this action to fill an empty candidate custom field with information from the candidate’s application.

Co-pilot only fills the field when it can determine a clear value. Existing values are never overwritten, and the field is left empty if the information is missing or unsuitable. Co-pilot cannot create custom fields or add options to existing fields.

Supported field types

You can select one of the following field types for each task:

The selected field must be visible, non-private, and allow updates from stage triggers. It must also accept the type of value Co-pilot returns.

Keep the following in mind when selecting a field:

Changes to the selected field can affect your task. If you delete or restrict the field, or remove required options, you will need to review and update the task.

Use this action to add existing candidate tags based on the information available to Co-pilot.

Only tags selected when setting up the task can be added. Co-pilot cannot create tags or add tags that aren't included in the selection. Existing tags remain unchanged, and tags that aren't supported by the candidate’s information are not added.

Choose which tags to add

When verifying your selection, Co-pilot checks the company’s most-used candidate tags, ranked by usage count and then by name. Less-used tags may not appear in the suggested selection, even if they're mentioned in your prompt.

Selecting All tags refers to the tags included in the saved selection, not every tag in your company. Tags created after you set up the task are not automatically added to the selection.

If a selected tag is no longer available

If any selected tag is deleted or disabled for candidates, the task fails, and no tags are added. You will then need to update the selection, verify it again, and save the task.

Use this action to remove selected candidate tags based on the conditions you configure.

When verifying your selection, Co-pilot checks the company’s most-used candidate tags, ranked by usage count and then by name. Only selected tags that the candidate currently has can be removed. Other tags remain unchanged.

Choose when to remove tags

You can configure the task to remove tags in two ways:

If the candidate has no selected tags that meet the removal conditions, the task will still be completed successfully without making any changes.

If a selected tag is no longer available

If any selected tag is deleted or disabled for candidates, the task fails, and no tags are removed. You will then need to update the selection, verify it again, and save the task.

Use this action to create a to-do with a title and description based on the information available to Co-pilot.

If information is missing, Co-pilot explains the gaps in the to-do description. For tasks without a condition, a to-do is still created even when information is limited. If the configured condition is not met, no to-do is created.

Set the assignee and due date

The assignee and due date are determined by the trigger settings, not by your prompt.

You can leave both the assignee and due date empty. If the assigned person has been deleted or is no longer part of the hiring team, the to-do is created without an assignee.

Notifications

When a to-do is created, the assignee receives an in-app notification. No specific assignment email is sent, but the notification may appear in their unread-notification digest if enabled.

Unassigned to-dos do not trigger notifications.

If you have our add-on feature Audit log enabled, you can find entries from Co-pilot about the candidates. These entries show whether the task succeeded or failed, which action was performed, and the related job and trigger IDs. If a configuration is invalid, the entry may also include the reason.

A successful run doesn’t always mean a change was made. Co-pilot may complete a task without taking action, for example, when there are no matching tags to remove. Check the candidate’s activity and the relevant fields, tags, or to-dos to confirm the outcome.