{"id":48211131,"url":"https://github.com/techservicesillinois/mss-power-automate-flows","last_synced_at":"2026-04-04T18:48:34.918Z","repository":{"id":88274539,"uuid":"503138180","full_name":"techservicesillinois/mss-power-automate-flows","owner":"techservicesillinois","description":"JSON for Power Automate flows","archived":false,"fork":false,"pushed_at":"2024-06-15T15:19:16.000Z","size":335,"stargazers_count":1,"open_issues_count":0,"forks_count":0,"subscribers_count":3,"default_branch":"main","last_synced_at":"2024-06-15T16:46:31.669Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/techservicesillinois.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2022-06-13T22:52:58.000Z","updated_at":"2024-06-15T16:46:33.679Z","dependencies_parsed_at":"2024-05-31T20:45:23.101Z","dependency_job_id":null,"html_url":"https://github.com/techservicesillinois/mss-power-automate-flows","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/techservicesillinois/mss-power-automate-flows","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/techservicesillinois%2Fmss-power-automate-flows","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/techservicesillinois%2Fmss-power-automate-flows/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/techservicesillinois%2Fmss-power-automate-flows/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/techservicesillinois%2Fmss-power-automate-flows/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/techservicesillinois","download_url":"https://codeload.github.com/techservicesillinois/mss-power-automate-flows/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/techservicesillinois%2Fmss-power-automate-flows/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":31409470,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-04-04T10:20:44.708Z","status":"ssl_error","status_checked_at":"2026-04-04T10:20:06.846Z","response_time":60,"last_error":"SSL_read: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2026-04-04T18:48:34.296Z","updated_at":"2026-04-04T18:48:34.908Z","avatar_url":"https://github.com/techservicesillinois.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# mss-power-automate-flows\n \nThis repo contains some sample flows I have created to automate tasks for myself, the most common being to receive a report file from a particular source, import it to a Sharepoint list, and then update graphs, etc., based on that. Some of the more complex changes were easier to work with in code, so I developed a couple flows that allow me to download JSON definitions for the flows, update them in a text editor, and then reimport them. \n\n## Format\n\nEach flow is represented by two JSON files--a definition file and a connection references file. They are named using the id of the flow (as generated by the \"Backup My Flows to Sharepoint\" flow). Definition file is named as just the flow ID (e.g. `7bd62a15-ab20-4d5a-ad9e-5d28bab1c99f.json`) and the connection references file is the flow ID + \"-conn\" (e.g. `7bd62a15-ab20-4d5a-ad9e-5d28bab1c99f-conn.json`).\n\n## Folder Structure\n### Flow JSON Tools\n\nTwo flows that [export a copy of all existing flows](Flow%20JSON%20Tools/Backup%20My%20Flows%20to%20Sharepoint) to a specified Sharepoint/OneDrive folder and accept [uploads of an existing flow](Flow%20JSON%20Tools/Update%20Flow%20from%20JSON) to update that flow. Currently the flow must already exist, but I plan to add another option to create a new flow from existing JSON.\n\nThese flows also contain a .zip import that can be used to import the flows initially into the Power Automate interface. In Power Automate, click \"My Flows\" and then \"Import-\u003e\".\n![Import .zip file in Power Automate](-images/import-power-automate.png)\n\n### General Flows\n\nThese are the flows I've created. The email ones (beginning with \"Email - \") are basically the same; they just check for a specific type of email and then give the attached file a specific name to prepare for the [Update Lists](General%20Flows/Update%20Lists) flow, which imports those files based on the naming conventions in the Email flows. [Clean Inbox](General%20Flows/Clean%20Inbox) is a simple tool that archives all emails that aren't either flagged or unread in my inbox and are older than 24 hours. ","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ftechservicesillinois%2Fmss-power-automate-flows","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Ftechservicesillinois%2Fmss-power-automate-flows","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ftechservicesillinois%2Fmss-power-automate-flows/lists"}