Short answer: Drop the "Venafi → Request Certificate" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Policy DN policyDN | string | Required | Policy DN |
Subject (CN) subject | string | Required | Subject (CN). e.g. "example.com" |
SAN DNS Names sanDns | string | Optional | Comma-separated |
{"policyDN": "{{trigger.policyDN}}","subject": "example.com","sanDns": "{{trigger.sanDns}}"}
{"Guid": "guid-123","CertificateDN": "\\VED\\Policy\\Certificates\\example.com"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.