Workflows let you compose reusable automation across the certificate lifecycle — issuing, renewing, deploying, revoking, notifying — using a declarative model of trigger → conditions → steps → notifications. They are defined per workspace, versioned, and every execution is captured for replay and audit.
Workflows

What it is

A workflow is a sequence of steps that runs automatically when its trigger fires, optionally gated by conditions and human approvals. Every execution is persisted with per-step output and timing, so you can debug failures and replay a failed run after fixing the underlying issue.

When to use it

  • Auto-renew wildcard certificates that match a specific naming pattern on a nightly schedule.
  • Pause issuance of production certificates until a security lead approves.
  • Send a Slack notification every time a certificate is deployed to a load balancer.
  • Trigger a discovery scan from an external CI system via a webhook.
  • Run a compliance report and email it to stakeholders every quarter.

Trigger types

TriggerTypical use
manualAd-hoc bulk operations from the dashboard or API
scheduleNightly reconciliation, weekly reports (cron expression)
eventAuto-remediation when certificate.expiring, discovery.new, or alert.fired
apiExternal systems trigger via the workflow’s webhook URL

Step action types

ActionPurpose
renew_certificateTrigger renewal for a certificate
deploy_certificatePush a certificate to agents, load balancers, or clusters
revoke_certificateRevoke and publish to CRL
create_approvalInsert an approval request and pause the workflow
notifySend to one or more notification channels
webhookPOST to an external URL with a signed payload
waitSleep for a duration or until a condition
run_workflowNested workflow invocation

Set it up

1

Open the workflow builder

Go to Automation > Workflows and click New workflow.
2

Choose a trigger

Select the trigger type. For schedules, enter a cron expression. For events, choose the event type from the dropdown. For API triggers, copy the generated webhook URL.
3

Add conditions (optional)

Click Add condition to gate the workflow. For example: only run when certificate.commonName starts with *. and daysUntilExpiry is less than 30.
4

Add steps

Click Add step and choose an action. Steps run in order; each step can reference the trigger payload and prior step outputs using template variables.
5

Add an approval step (optional)

Toggle Requires approval on any step that should pause for human review. Select the approvers from your workspace members. The workflow resumes automatically once the required approvers act.
6

Enable and save

Toggle Enabled and click Save workflow. The workflow is live immediately.

What you’ll see

Automation > Workflows shows the list of workflows with their trigger type, last run status, and enabled/disabled state. Click a workflow to see its execution history. Click any execution row to drill into per-step output, timing, and error messages.
Every workflow create, update, enable/disable, and execute action is written to the audit log. Failed executions preserve step-level error messages so you can replay after fixing the underlying issue.
Workflows run with the permissions of the user who triggered them (for manual and API triggers) or the workflow’s creator (for schedules). Role checks happen inside each step — a workflow cannot escalate privileges.
The API surface for workflow management is documented at API Reference.

Approvals

Add human gates to workflows that touch production certificates.

Notifications

Wire workflow events into Slack, PagerDuty, or webhooks.

Alerts

Turn alert rules into workflow triggers.