Skip to main content
Automations connect a Harly event to one or more actions. Use them for repeatable notifications and task creation, while keeping consequential hiring decisions explicit and human-owned.

​
A safe automation shape

Typical examples:
  • Candidate applies → notify a recruiting channel.
  • Application enters interview stage → create a coordinator task.
  • Interview completed → request a scorecard from the interviewer.
  • Offer accepted → notify the hiring team.

​
Configure a workflow

1

Open Automations

Select Automations in the left sidebar and choose New workflow.
2

Choose a trigger

Select a supported trigger event:
3

Add conditions

Narrow the trigger with conditions:
  • Job — only fire for a specific job or department.
  • Stage — only fire when entering a specific pipeline stage.
  • Status — only fire when a field has a specific value.
Conditions prevent a notification workflow from firing on every job in the workspace when you only want it for one department.
4

Configure an action

Choose an action:HTTP actions support workspace secret references so credentials do not appear in workflow payloads. Outbound requests use the same SSRF protections as webhooks — loopback, private, and metadata addresses are blocked.
5

Preview and enable

Run the workflow preview to confirm the trigger and action match your intent. Enable the workflow. It begins processing new events immediately.

​
Reliability and run history

Each run records:
  • The trigger event that fired it
  • The conditions that matched
  • The action configuration
  • The result (success, failure, or skipped)
  • The error message if it failed
Open a workflow to see its run history. Retry transient failures from the run detail. Fix configuration failures before replaying — a misconfigured action retries successfully once you correct it.
Do not build an automation that rejects candidates, deletes records, or sends an offer without a human review step. Keep irreversible actions explicitly human — automate the preparation and notification, not the decision.

​
HTTP action details

The HTTP action sends a POST request to the configured URL with a JSON payload matching the trigger event’s schema. Configure a secret to verify the request:
The receiver must return 2xx within 10 seconds. Failed requests are retried by the scheduler using the same retry policy as webhooks.

​
Next steps

Webhooks

Subscribe to domain events from external systems.

API overview

Build richer integrations against the Harly API.

Notifications

Connect Slack, Discord, and Telegram.

Tasks and scorecards

The task model automations create work for.