← All N8N workflows
Messaging & emailAggregateHTTP RequestIfNo OpRespond To Webhook

Events Webhook Trigger

Configured with Aggregate, HTTP Request, Respond To Webhook, S3, and additional nodes. Review the connections and setup before adapting this template.

Workflow preview
TransformParse WebhookEdit FieldsWeb / APIClose Modal PopupRespond To WebhookWeb / APIIdea Selector ModalHTTP RequestRoutingRoute MessageSwitchRoutingRoute Message1SwitchWeb / APICreate FolderHTTP RequestWeb / APISelect FolderHTTP RequestRoutingLoop Over ItemsLoop Over ItemsTransformSuccess ResponseEdit FieldsRoutingCheck if uploadedsuccessfullyIfRoutingmove on to nextNo OpRoutingNo Operation, donothingNo OpTransformAggregateAggregateRoutingRoute ActionSwitchTriggerWebhookWebhookTransformFailure ResponseEdit FieldsWeb / APIRespond to SlackWebhook - SuccessRespond To WebhookWeb / APIRespond to SlackWebhook - No ActionRespond To WebhookWeb / APIDownload File BinaryHTTP RequestFiles / mediaUpload to S3 BucketS3MessagingPost Image to ChannelSlackTransformSplit Out FilesSplit Out

Node categories in this workflow

  • Transform
  • Web / API
  • Routing
  • Trigger
  • Files / media
  • Messaging

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
NodeCategoryTypeOperation
Parse WebhookTransformEdit FieldsSee node parameters
Close Modal PopupWeb / APIRespond To WebhookSee node parameters
Idea Selector ModalWeb / APIHTTP RequestPOST
Route MessageRoutingSwitchSee node parameters
Route Message1RoutingSwitchSee node parameters
Create FolderWeb / APIHTTP RequestPOST
Select FolderWeb / APIHTTP RequestPOST
Loop Over ItemsRoutingLoop Over ItemsSee node parameters
Success ResponseTransformEdit FieldsSee node parameters
Check if uploaded successfullyRoutingIfSee node parameters
move on to nextRoutingNo OpSee node parameters
No Operation, do nothingRoutingNo OpSee node parameters
AggregateTransformAggregateSee node parameters
Route ActionRoutingSwitchSee node parameters
WebhookTriggerWebhookSee node parameters
Failure ResponseTransformEdit FieldsSee node parameters
Respond to Slack Webhook - SuccessWeb / APIRespond To WebhookSee node parameters
Respond to Slack Webhook - No ActionWeb / APIRespond To WebhookSee node parameters
Download File BinaryWeb / APIHTTP RequestSee node parameters
Upload to S3 BucketFiles / mediaS3upload
Post Image to ChannelMessagingSlackSee node parameters
Split Out FilesTransformSplit OutSee node parameters

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

  • s3
  • slackApi

Workflow notes

Events Webhook Trigger

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

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

Display Modal Popup

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

🙋 Don't forget your slack credentials!

🙋 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.

Split Files out for processing

Split Files out for processing

Takes the single response from Slack and splits out the file objects to loop across them.

Loop through files to upload to S3 Cloudflare Bucket

Loop through files to upload to S3 Cloudflare Bucket

The success and failure path report back to slack once all files are uploaded.

Combine Success and failure responses in final message

Combine Success and failure responses in final message

Allows for the workflow to fail gracefully.

Events Webhook Trigger

Events Webhook Trigger

Purpose and structure

This folder contains the Events Webhook Trigger workflow. Its executable nodes use aggregate, httpRequest, if, noOp, respondToWebhook, s3, set, slack, splitInBatches, splitOut, switch, 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/Splitout/0650_Splitout_Webhook_Create_Webhook.json MIT; preserve source notices.

More in Messaging & email