Handle certificate requests inside Slack and keep security in the loop. Team members submit a domain in a simple Slack modal. The flow checks the domain for risk and either issues the certificate or asks for a quick review.

Incoming Slack events reach an n8n Webhook and are parsed into clean fields. A modal opens with views open so users can enter the domain. The flow gathers the user email and team details through sub workflows, then checks the domain with VirusTotal. When there are zero malicious reports, Venafi TLS Protect Cloud generates a CSR and issues the certificate. If risk shows up, OpenAI writes a short summary, and Slack posts a review message with context so a teammate can approve. Respond nodes close the modal fast so Slack does not time out.

You will need a Slack app, a VirusTotal key, Venafi TLS Protect Cloud access, and an OpenAI key. Set your Venafi application and template IDs. Most clean domains can be approved automatically, which cuts wait time and support load. This is great for IT and security teams that support developers who need HTTPS for new domains.

• Webhook entry point receives Slack events and interactions
• Slack modal is opened with views open to collect the domain
• Domain validation and mapping of fields into clean JSON
• VirusTotal check summarizes risk before any certificate action
• Conditional routing auto issues or routes to manual review
• Venafi TLS Protect Cloud generates CSR and requests the certificate using your template
• Sub workflows resolve Slack user ID to email and team info then merge the data
• OpenAI drafts a short risk summary for reviewers in Slack
• Respond to Webhook nodes close modals and keep Slack within time limits

• Reduce manual work from one hour to five minutes per request
• Automate up to 80 percent of low risk certificate requests
• Improve accuracy by capturing inputs in a Slack modal
• Connect Slack, VirusTotal, Venafi TLS Protect Cloud and OpenAI
• Handle many requests at once with parallel steps and merges
• Send clear audit friendly messages with requester and team details

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Slack, VirusTotal, Venafi TLS Protect Cloud and OpenAI. See the Tools Required section above for links to create accounts with these services.
3. In the n8n credentials manager, create a Slack credential. If unsure, double click a Slack node like Venafi Request Certificate, choose Create new credential, and follow the on screen steps to connect your bot token.
4. In the credentials manager, add a VirusTotal API Key credential. Get your API key from the VirusTotal account settings page and paste it into n8n.
5. In the credentials manager, add Venafi TLS Protect Cloud credentials. Use your Venafi API key or service account details as required by your organization.
6. In the credentials manager, add an OpenAI API Key credential. Create an API key in your OpenAI account and paste it into n8n.
7. Open the Webhook node and copy the Production URL. In your Slack app, enable Interactivity and Events, then set the request URL to this webhook. Add required scopes like chat write and users read, then install the app to your workspace.
8. Open the Venafi Request Certificate node and confirm the Slack credential is selected. Review the modal JSON. Update any labels to fit your policy.
9. Open both Venafi TLS Protect Cloud nodes and set your application ID and certificate issuing template ID. Confirm generate CSR is turned on if you want CSR generation.
10. Check the Execute Workflow nodes. Select the correct sub workflows that return the Slack user email and the team details. Save your choices.
11. Test the flow. Trigger the Slack command or event that opens the modal, submit a domain, and watch the logs in n8n. You should see VirusTotal results and either an auto confirmation or a review message in Slack.
12. If Slack times out, make sure the Respond to Webhook nodes are connected right after the initial routes. If Venafi errors, verify application and template IDs. If VirusTotal limits are reached, space out tests or upgrade your plan.