n8n workflow template · 23 nodes · Venafi TLS Protect Cloud
Venafi Cloud Slack Cert Bot is a free n8n workflow template that starts when its webhook receives an HTTP request and works with Venafi TLS Protect Cloud, OpenAI and Slack. It has 23 nodes, 1 of them AI nodes (OpenAI). The notes inside the workflow say: “The first node receives all messages from Slack API via Subscription Events API. You can find more information about setting up the subscription events API by clicking here.” To run it, you add your own credentials for OpenAI API, Slack API, Venafi TLS Protect Cloud API and Virus Total API.
The text below comes from the sticky notes inside the workflow. We removed links, code samples and anything that looks like a key or token.
The first node receives all messages from Slack API via Subscription Events API. You can find more information about setting up the subscription events API by clicking here.
The second node extracts the payload from slack into an object that n8n can understand.
This section of the workflow is designed to efficiently manage and route messages and submissions from Slack based on specific triggers and conditions. When a Slack interaction occurs—such as a user triggering a vulnerability scan or generating a report through a modal—the workflow intelligently routes the message to the appropriate action
Purpose: This mechanism ensures that all interactions within Slack are handled quickly and accurately, automating responses and actions in real-time to enhance user experience and workflow efficiency.
This section pops open a modal window that is later used to send data into Virustotal, then depending on those results, to Venafi or Slack for manual approval.
Modals can be customized to perform all sorts of actions. And they are natively mobile! Additionally, messages themselves can perform actions if you include inputs like buttons or field inputs.
Learn more about them by clicking here
The first node receives all messages from Slack API via Subscription Events API. You can find more information about setting up the subscription events API by clicking here.
The second node extracts the payload from slack into an object that n8n can understand.
This section of the workflow contains 2 subworkflows that translate the Slack User ID to an email and name, and the Slack Team ID into the team name and Avatar of the team to make the slack messages more visual. This allows you to reuse these flows like you would use a function in code.
These nodes run parallel to each other so they will not override the data generated by each thread, and then are joined using the Merge nodes.
Contextual data from the Slack user's webhook is used to gather the needed contextual data, such as the name of the Slack team/group the user is in and their email and name if needed. Please note this section is still a proof of context and may not work exactly as expected.
For automatic CSR Generation to work, ensure you have a Vsatelite deployed and active.
This section of the workflow is designed to efficiently manage and route messages and submissions from Slack based on specific triggers and conditions. When a Slack interaction occurs—such as a user triggering a vulnerability scan or generating a report through a modal—the workflow intelligently routes the message to the appropriate action
Contextual data from the Slack user's webhook is used to gather the needed contextual data, such as the name of the Slack team/group the user is in and their email and name if needed.
For automatic CSR Generation to work, ensure you have a Vsatelite deployed and active.
This section pops open a modal window that is later used to send data into TheHive.
Modals can be customized to perform all sorts of actions. And they are natively mobile! You can see a screenshot of the Slack Modals on the right.
Learn more about them by clicking here
The text below comes from the sticky notes inside the workflow. We removed links, code samples and anything that looks like a key or token.
Our Venafi Slack CertBot is strategically designed to facilitate immediate security operations directly from Slack. This tool allows end users to request Certificate Signing Requests that are automatically approved or passed to the Secops team for manual approval depending on the Virustotal analysis of the requested domain. Not only does this help centralize requests, but it helps an organization maintain the security certifications by allowing automated processes to log and analyze requests in real time.
Deploy this bot within your Slack environment to significantly enhance the efficiency and responsiveness of your security operations, enabling proactive management of CSR's.
Thankfully n8n makes it easy, as long as you've added credentials to a normal slack node, these http nodes are a snap to change via the drop down.
This workflow currently uses OpenAI to power it's responses, but you can replace the AI Agent node below and set your own local AI LLM using the n8n options offered.
The 23 nodes in file order (sticky notes excluded). Branches and connections determine execution order in n8n:
Configure your own credentials after importing. Create each credential in n8n, then select it in the node.
Do you need somewhere to run it? Read our guide to self-hosted n8n.
We can adapt this workflow to your apps, data and process, then deploy and support it.
Contact Us