Events Webhook Trigger

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.

Efficient Slack Interaction Handling with n8n

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:

• Dynamic Routing: Uses conditions to determine the nature of the Slack interaction, whether it's a direct command to initiate a scan or a request to generate a report.
• Modal Management: Differentiates actions based on modal titles and callback_ids, ensuring that each type of submission is processed according to its context.
• Streamlined Responses: After routing, the workflow promptly handles the necessary responses or actions, including closing modal popups and responding to Slack with appropriate confirmation or data.

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.

Display Modal Popup

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

Enhance Security Operations with the Venafi Slack CertBot!

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.

Workflow Highlights:

• Interactive Modals: Utilizes Slack modals to gather user inputs for scan configurations and report generation, providing a user-friendly interface for complex operations.
• Dynamic Workflow Execution: Integrates seamlessly with Venafi to execute CSR generation and if any issues are found, AI can generate a custom report that is then passed to a slack teams channel for manual approval with the press of a single button.

Operational Flow:

• Parse Webhook Data: Captures and parses incoming data from Slack to understand user commands accurately.
• Execute Actions: Depending on the user's selection, the workflow triggers other actions within the flow like automatic Virustotal Scanning.
• Respond to Slack: Ensures that every interaction is acknowledged, maintaining a smooth user experience by managing modal popups and sending appropriate responses.

Setup Instructions:

• Verify that Slack and Qualys API integrations are correctly configured for seamless interaction.
• Customize the modal interfaces to align with your organization's operational protocols and security policies.
• Test the workflow to ensure that it responds accurately to Slack commands and that the integration with Qualys is functioning as expected.

Need Assistance?

• Explore Venafi's Documentation or get help from the n8n Community for more detailed guidance on setup and customization.

Deploy this bot within your Slack environment to significantly enhance the efficiency and responsiveness of your security operations, enabling proactive management of CSR's.

🙋 Don't forget your slack credentials!

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.

Run Workflows within other Workflows like Functions

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.

URL Analysis with VirusTotal

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.

Automatic CSR Generation via Venafi

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.

Send Contextual Message to Slack

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

Efficient Slack Interaction Handling with n8n

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:

Parse Response with AI Model

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.

Manual CSR Generation via Venafi

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.

Events Webhook Trigger

Purpose and structure

This folder contains the Events Webhook Trigger workflow. Its executable nodes use executeWorkflow, httpRequest, if, merge, noOp, openAi, respondToWebhook, set, slack, switch, venafiTlsProtectCloud, webhook. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

Webhook

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Webhook/0581_Webhook_Slack_Create_Webhook.json MIT; preserve source notices.