Short answer: Drop the "Venafi → List Certificates" 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 |
|---|---|---|---|
Limit limit | number | Optional | Limit |
Folder DN folder | string | Optional | Folder DN |
{"limit": "{{trigger.limit}}","folder": "{{trigger.folder}}"}
{"TotalCount": 100,"Certificates": [{"DN": "\\VED\\Policy\\Certificates\\example.com","Name": "example.com","CreatedOn": "2026-01-01T00:00:00Z"}]}
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.