Gerico1007
commented
1 week ago Action Plan for Flowise Chat Flow to Review GitHub Updates and Generate a PowerPoint Summary
Connect to GitHub API Goal: Retrieve daily changes in the “ea” repository to monitor progress.
Steps:
Step 1: Open Flowise and start a new chat flow.
Step 2: Add a REST API node and configure it to connect to GitHub’s API.
Step 3: Set the base URL as https://api.github.com/.
Step 4: Under headers, add an authorization token (generate a personal access token from your GitHub account for this purpose).
Step 5: Specify the repository endpoint. For example: GET /repos/{username}/ea/commits.
Step 6: Test this setup by running the flow to verify if it successfully retrieves commit history.
Filter Daily Updates Goal: Retrieve only the updates made within the current day to keep track of daily progress.
Steps:
Step 1: Add a filter or conditional node to the flow after the GitHub API connection node.
Step 2: Set a condition that filters based on the date and time range. For example, use the since parameter in the API request URL with the current date.
Step 3: Use a function to get the current date and format it in a way compatible with GitHub’s API (ISO 8601 format, e.g., 2024-11-10T00:00:00Z).
Step 4: Run a test to ensure the filter retrieves only today’s commits and changes, discarding previous days’ updates.
Fetch Issue Details Goal: Identify goals set as GitHub issues to track how daily work aligns with them.
Steps:
Step 1: Add another API node to connect with the GitHub issues endpoint. Example endpoint: GET /repos/{username}/ea/issues.
Step 2: Configure the request to fetch issues with a specific label or keyword (e.g., “goal”).
Step 3: Add a filter to select only open issues if you want to focus on ongoing goals.
Step 4: Run the flow to verify that it pulls the issues correctly and lists only those marked as goals or relevant keywords.
Generate Summary Goal: Format and link daily changes to specific goals for clear documentation.
Steps:
Step 1: Insert a text-processing or formatter node in the Flowise sequence after the API and filtering nodes.
Step 2: Use text concatenation to create a structured summary. Format each section to include:
Commit details (e.g., commit message, author, date).
Related goals (extracted from issues).
Step 3: Configure the node to add headings for each goal and list related commits as bullet points beneath them.
Step 4: Run the flow and verify if the output summary clearly links each daily change to relevant goals.
Convert to PowerPoint Goal: Export the formatted summary into a PowerPoint presentation.
Steps:
Step 1: Set up a connector node to link Flowise with a PowerPoint generation tool (either through API integration or file conversion).
Step 2: Configure the output format for PowerPoint. Create a slide template if possible, setting up titles, sections, and text placeholders.
Step 3: Map the content from the summary node into the PowerPoint template. Each goal and its related updates should have its own slide or section.
Step 4: Test this step by generating a sample PowerPoint file and reviewing its structure to ensure clarity and organization.
Automate Workflow Goal: Schedule this process to run daily, automating the creation of the summary and PowerPoint presentation.
Steps:
Step 1: Open your task scheduler on your computer or use Flowise’s built-in scheduling feature (if available).
Step 2: Set a time for the flow to run each day (e.g., 8:00 PM daily).
Step 3: Enable the schedule and ensure Flowise can execute the entire sequence automatically.
Step 4: Run a trial automation to verify it successfully completes each step, generating the daily summary and PowerPoint without manual input.
Testing each step and verifying that the nodes work as expected will ensure the entire flow functions smoothly, generating your daily summaries and linking them to your goals.
here's information for my 1rst flow