Integrate Monday with SharePoint and Office365 Power Automate

 I must say it was fairly simple.

Step 1 - Buy Premium Power Automate Account

BTW you can try the Trial and get 25 licenses for free for 1 month.

You need to go to your admin center to the marketplace (or ask IT) for the Power Automate Premiun license, and assign it to the user that is going to create the automation. 

He also must be board admin in the Monday.

link is like this https://admin.microsoft.com/?source=applauncher#/catalog



Step 2 - Install app on Monday

This app just create some webhooks for Power Automate and the connection ect. IMPORTANT this is not an official MS app, just some 3rd party. 

You could develop hooks if you have restrictions.


This is what you need to see PER BOARD to know its working. Again you must have Board Admin role.


Step 3 - Start a Monday Automation

Create a flow and search monday or user the main search bar to get suggestion

IMPORTANT - when you start he will open a popup with 2 buttons to complete the connector. You need to click both (not at once ☺) and follow instructions.

TIPS:

1. The title columns is always "Item Name", even if the user changes it.

2. when you "quick create" from the table a new row, instead of a form, you dont get on "create item" anything other than Item Name.

3. you dont need ParseJson, he knows your monday rows

4. people column comes as array of string with full name. Need to search for exact names if needed











Comments

Post a Comment

Popular posts from this blog

OverTheWire[.com] Natas Walkthrough - JUST HINT, NO SPOILERS

game portal: http://overthewire.org/wargames/natas/ PASSWORDS for each level are stored in /etc/natas_webpass/natasX I made this walkthrough for people like me, i needed some help, but didnt want the spoiler, so here i will give you all the information needed to pass each level, yet not the solution. For levels needed custom web request i made a different post for powershell and javascript  with how-to's, since is a piece of learning for itself, and also for those of us that play at work and have only powershell at their hands. Although its not a complete spoiler there, its quite most of the solution so try yourself 1st. Natas The Natas game is from basic to advances web hacking. Every few levels is about whole new exploitation (with some harder ones doing comeback later), so a lot of learning. If you're new, you're the reason i am writing so much even for the 1st level, just please google EVERY topic you see, since in the following levels i assume you know the
Read more

SOLVED The item could not be indexed successfully because the item failed in the indexing subsystem

if you got an error like this The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Failed to recover content group; Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = 04081656-B51B-4DCD-96D4-6DB2D2CEEEE7 ) as well as these: The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Caught exception when preparing generation GID[7]: (Previous generation (last=GID[6], curr=GID[7]) is still active. Cannot open GID[7]); Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = 92EB0180-C086-4853-BED8-F4878D9748AD ) the solution for me was to clear configuration cache (PS)  and then restart SP Search Services. THX to m
Read more

Asp.Net Ending Response options, Response.End() vs CompleteRequest()

this blog is for any1 who get the ThreadAbortException when caling Response.End(), and then tried the other options such as HttpContext.Current.ApplicationInstance.CompleteRequest() and found out that there was no replacement. i'll start with the bottom line: if you want to stop right now your response and send it as is you dont have any other option other than Response.End(), period and it's the right thing to throw that EX in that case. the answer is its because there is the "HTTP pipeline" and the "Asp.Net pipeline", and CompleteRequest() cuts the HTTP pipeline but not the Asp.Net one so everything that is from handlers forwars (including all page events) continues but your part, the asp one, stays in your hands so that no information will be lost, so ur suppose to manage your code currectly, since information lost is really a bad thing, although in most cases we use Response.End() we know what we are losing and we want it. see this short article ab
Read more