Setting Up Slack App Event Subscriptions
Configured with Agent, OpenAI Chat Model, Memory Buffer Window, Microsoft Outlook Tool, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- AI & models
- Messaging
- Data store
- Web / API
- Routing
- Transform
- Trigger
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.
| Node | Category | Type | Operation |
|---|---|---|---|
| OpenAI Chat Model | AI & models | OpenAI Chat Model | See node parameters |
| Search All Outlook Events | Messaging | Microsoft Outlook Tool | event |
| Create New Calendar Event | Messaging | Microsoft Outlook Tool | event / create |
| Get Available Calendars | Messaging | Microsoft Outlook Tool | calendar |
| Simple Memory | Data store | Memory Buffer Window | See node parameters |
| Outlook Calendar Assistant | AI & models | Agent | See node parameters |
| Send Reply | Messaging | Slack | See node parameters |
| Respond to Challenge | Web / API | Respond To Webhook | See node parameters |
| Is Auth Challenge? | Routing | If | See node parameters |
| Get Message | Transform | Edit Fields | See node parameters |
| On BOT/APP Mention | Trigger | Webhook | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- 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
microsoftOutlookOAuth2ApiopenAiApislackApi
Workflow notes
This n8n template demonstrates how easy it is to build an Outlook Calendar Assistant powered by an AI agent equipped with Tools.
This n8n template demonstrates how easy it is to build an Outlook Calendar Assistant powered by an AI agent equipped with Tools.
n8n's AI agents makes it easy to build powerful assistants which can interact with your existing services and tools. With little effort, you can expose such an agent to team members and colleagues though something like Slack and enable a company-wide productivity booster.
How it works
- A Slack Trigger node is configured to catch "bot mentions" events in a designated channel.
- The message is parsed using the Edit fields node to extract only the required attributes of the event.
- An AI Agent equipped with Outlook Calendar Tools enables question and answer capability for the organisation's shared calendars and events.
- The AI agent's response is sent back to Slack as a reply to the user's query.
How to use
- The workflow is triggered via @mention-ing the bot followed by the query. eg. "@bot how many meetings does Paul have to attend to this week?"
- To start listening to real mentions, you must activate the workflow and set it to production mode. You must use the production webhook URL for the event subscription.
Need Help?
1. Listen for Bot Mentions
1. Listen for Bot Mentions
Read more about Webhook Trigger
Example:
@bot how many meetings does Paul have to attend to this week?
2. AI Agent with Outlook Calendar Tools
2. AI Agent with Outlook Calendar Tools
Learn more about the AI Agent node
This agent has 3 Outlook tools to search, browse and even create calendar events for the user. Agents are great in that we don't have to tell the agent what and when to use the tools - it'll make that decision on its own!
3. Reply to User
3. Reply to User
Learn more about the Slack node
Simple sends a reply back to the user answering their query. Of course, this is the simplest case and it'll be up to you to handle multi-turn conversation as needed.
Setting Up Slack App Event Subscriptions
Setting Up Slack App Event Subscriptions
- Go to https://api.slack.com/apps
- Create or Select your App
- Under Features, click into "Event Subscriptions"
- On this page, toggle on the "Enable Events" option
- Enter the production URL of this template - your workflow but be active and publicly accessible for this to work.
- Slack will issue a "challenge" request to this workflow which will respond and verify the subscription.
- If successful, under "subscribe to bot events", find and select the "app_mention" option.
- Hit "save changes" at the bottom of the page.
- This workflow should now trigger when your bot is "@mention" in the channel.
Setting Up Slack App Event Subscriptions
Setting Up Slack App Event Subscriptions
Purpose and structure
This folder contains the Setting Up Slack App Event Subscriptions workflow. Its executable nodes use agent, if, lmChatOpenAi, memoryBufferWindow, microsoftOutlookTool, respondToWebhook, set, slack, 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
On BOT/APP Mention
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/0834_Webhook_Slack_Create_Webhook.json MIT; preserve source notices.