See llms.txt for all machine-readable content.
This workflow automates the Developer Q&A Classification and Documentation process using Slack, Azure OpenAI GPT-4o, Notion, Airtable, and Google Sheets.
Whenever a new message is posted in a specific Slack channel, the workflow automatically:
π’ Slack Channel Trigger β Developer Q&A
Triggers the workflow whenever a new message is posted in a specific Slack channel. Captures message text, user ID, timestamp, and channel info.
π§© Validate Slack Message Payload (IF Node)
Ensures the incoming message payload contains valid user and text data.
β
True Path β Continues to extract and process the message
β False Path β Logs error to Google Sheets
π» Extract Question Metadata (JavaScript)
Cleans and structures the Slack message into a standardized JSON format β removing unnecessary characters and preparing a clean βquestion objectβ for AI processing.
π§ Classify Developer Question (AI) (Powered by Azure OpenAI GPT-4o)
Uses GPT-4o to semantically compare the question with an internal FAQ dataset.
If a match is found β Marks as answered and generates a canonical response
If not β Flags it as unanswered
π§Ύ Parse AI JSON Output (Code Node)
Converts GPT-4oβs text output into structured JSON so that workflow logic can reference fields like status, answer_quality, and canonical_answer.
βοΈ Check If Question Was Answered (IF Node)
If status == "answered", the question is routed to Notion for documentation; otherwise, itβs logged in Airtable for review.
π Save Answered Question to Notion FAQ
Creates a new Notion page under the βFAQβ database containing the question, AIβs canonical answer, and answer quality rating β automatically building a self-updating internal FAQ.
π Log Unanswered Question to Airtable
Adds unresolved or new questions into Airtable for manual review by the developer support team. These records later feed back into the FAQ training loop.
π¨ Log Workflow Errors to Google Sheets
Any missing payloads, parsing errors, or failed integrations are logged in Google Sheets (error log sheet) for transparent tracking and debugging.
β
Automates Slack Q&A classification
β
Builds and updates internal FAQs with zero manual input
β
Ensures all developer queries are tracked
β
Reduces redundant questions in Slack
β
Maintains transparency with error logs