ActionVenafiUpdated September 2026
How do I request a new Venafi certificate?
Short answer: You can request certificate in Venafi by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Venafi Request Certificate action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
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 |
Sample request
{"policyDN": "{{trigger.policyDN}}","subject": "example.com","sanDns": "{{trigger.sanDns}}"}
Returns
{"Guid": "guid-123","CertificateDN": "\\VED\\Policy\\Certificates\\example.com"}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Request Certificate.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Request Certificate.
What does the Request Certificate action do in Venafi?
Requests a new certificate from Venafi (TLS Protect Cloud or TPP) with the supplied CSR or subject details. Most often used as part of a renewal automation kicked off by the expiring-cert trigger.
What inputs does Request Certificate require?
Required: Policy DN, Subject (CN). Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Venafi returns an error?
The run history shows the failed step with its input and the error message Venafi returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Request Certificate support batch operations?
Run Request Certificate inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Venafi's rate limits.
More actions