Step 2: Connect Primary Services and Input Parameters

Define all source identifiers and connect the data collection services that run in parallel after setup.

1. Open Setup Parameters and set the placeholders to your values:
   • slackChannelId to <__PLACEHOLDER_VALUE__Slack channel ID to monitor__>
   • teamsChannelId to <__PLACEHOLDER_VALUE__Teams channel ID to monitor__>
   • gmailQuery to <__PLACEHOLDER_VALUE__Gmail search query__>
   • githubRepo to <__PLACEHOLDER_VALUE__GitHub repository name__>
   • confluenceSpaceKey to <__PLACEHOLDER_VALUE__Confluence space key__>
   • notionDatabaseId to <__PLACEHOLDER_VALUE__Notion database ID__>
   • lookbackHours to 1
2. Confirm parallel execution: Setup Parameters outputs to Retrieve Slack Posts, Fetch Teams Chats, Collect Gmail Threads, Retrieve GitHub Activity, Fetch Confluence Pages, and Retrieve Notion Records in parallel.
3. In Retrieve Slack Posts, set Operation to search and Limit to 100.
4. Credential Required: Connect your slackOAuth2Api credentials in Retrieve Slack Posts.
5. In Fetch Teams Chats, set Channel ID to {{ $('Setup Parameters').first().json.teamsChannelId }} and Resource to channelMessage.
6. Credential Required: Add Microsoft Teams credentials in Fetch Teams Chats (no credentials are currently configured).
7. In Collect Gmail Threads, set Filters → q to {{ $('Setup Parameters').first().json.gmailQuery }} and Limit to 100.
8. Credential Required: Connect your gmailOAuth2 credentials in Collect Gmail Threads.
9. In Retrieve GitHub Activity, set Repository to {{ $('Setup Parameters').first().json.githubRepo }}.
10. Credential Required: Add GitHub credentials in Retrieve GitHub Activity (none are configured).
11. In Fetch Confluence Pages, set URL to <__PLACEHOLDER_VALUE__Confluence API URL for getting pages__> and keep Authentication as genericCredentialType with Generic Auth Type httpBasicAuth.
12. Credential Required: Add HTTP Basic Auth credentials in Fetch Confluence Pages.
13. In Retrieve Notion Records, set Database ID to {{ $('Setup Parameters').first().json.notionDatabaseId }}.
14. Credential Required: Add Notion credentials in Retrieve Notion Records (none are configured).

Step 3: Combine and Review Content with AI

Aggregate inputs, summarize key knowledge, and return structured insights for downstream updates.

1. Ensure Retrieve Slack Posts and Fetch Teams Chats both connect into Combine All Inputs to merge content streams.
2. In Combine All Inputs, keep Mode set to combine and Combine By set to combineAll.
3. In AI Content Reviewer, set Text to {{ $json.content || $json.text || $json.body || $json.message || JSON.stringify($json) }} and keep Prompt Type as define.
4. Connect Anthropic Chat Engine as the language model for AI Content Reviewer and verify the model is claude-sonnet-4-5-20250929.
5. Credential Required: Connect your anthropicApi credentials in Anthropic Chat Engine.
6. Attach Structured Result Parser as the output parser to AI Content Reviewer with Schema Type set to manual.
7. Note: Structured Result Parser is a sub-node—add any required credentials to the parent AI Content Reviewer, not the parser.

Step 4: Filter Valuable Content and Prepare the Update Payload

Only useful insights should trigger updates; build the final payload that documents will receive.

1. In Validate Useful Content, confirm the boolean condition checks {{ $json.isValuable }} and routes only true items forward.
2. In Prepare Update Payload, set documentTitle to {{ $json.category + ': ' + $json.summary.substring(0, 50) }}.
3. Set updateContent to {{ $json.summary }} and metadata to {{ { category: $json.category, priority: $json.priority, source: $json.source, timestamp: new Date().toISOString() } }}.
4. Keep Include Other Fields enabled in Prepare Update Payload to preserve upstream data.

Step 5: Configure Document Updates and Notifications

Send the update payload to Notion and Confluence in parallel, then notify reviewers in Slack.

1. Confirm parallel execution: Prepare Update Payload outputs to both Update Notion Entry and Update Confluence Entry in parallel.
2. In Update Notion Entry, set the Operation to update and map the fields to the incoming payload from Prepare Update Payload.
3. Credential Required: Add Notion credentials in Update Notion Entry (none are configured).
4. In Update Confluence Entry, set URL to <__PLACEHOLDER_VALUE__Confluence API URL for updating page__> and Method to PUT.
5. Set JSON Body to {{ { version: { number: 2 }, title: $json.documentTitle, body: { storage: { value: $json.updateContent, representation: 'storage' } } } }} and keep Send Body enabled with Specify Body set to json.
6. Credential Required: Add HTTP Basic Auth credentials in Update Confluence Entry.
7. In Send Slack Review Alert, set Text to {{ '📝 Document Updated: ' + $json.documentTitle + '\n\nCategory: ' + $json.category + '\nPriority: ' + $json.priority + '\n\nSummary: ' + $json.summary + '\n\nPlease review the updated documentation.' }} and select your review channel.
8. Credential Required: Connect your slackOAuth2Api credentials in Send Slack Review Alert.

Step 6: Test and Activate Your Workflow

Run a manual test to validate data sources, AI output, updates, and alerts before enabling automation.

1. Click Execute Workflow and verify Setup Parameters passes values into the parallel data collection nodes.
2. Check that Combine All Inputs receives content and AI Content Reviewer returns structured fields like summary, category, priority, and isValuable.
3. Confirm Update Notion Entry and Update Confluence Entry both run when Validate Useful Content is true, and that Send Slack Review Alert posts a formatted message.
4. When successful, toggle the workflow to Active to enable the scheduled runs.