Hi all,
As there isn’t a built-in connector, I’ve spent a few weeks creating a Power Automate flow to pass Microsoft Forms data into Monday via the API.
I’ve used a lot of people’s posts and research, plus a lot of trial and error, but finally have a working version which I hope some people may find useful.
I won’t cover the Forms part of the flow, as there’s plenty of info about that, but there’s very little out there about using the HTTP connector to call the Monday API suite.
Unfortunately the HTTP connector is Premium, so you’ll need a license.
Starting with a simple one - I needed the person who submitted the form to be on a People column on the Monday board. The API needs a User ID, but all I have is an email, so I need to get all the users, then find the one I want:
Then a Parse JSON action with the following Schema:
{
“type”: “object”,
“properties”: {
“data”: {
“type”: “object”,
“properties”: {
“users”: {
“type”: “array”,
“items”: {
“type”: “object”,
“properties”: {
“email”: {
“type”: “string”
},
“id”: {
“type”: “integer”
}
},
“required”: [
“email”,
“id”
]
}
}
}
},
“account_id”: {
“type”: “integer”
}
}
}
Next add a Filter Array using the previous Parse JSON “user”, where the “email” is equal to the form responder. Make sure you use the “tolower” function as the filter is case sensitive
This will return an array, despite only having one match, so you also need to add a “Compose” action and use the expression “first(body(‘Filter_array’))?[‘id’]” to return just the first item from the array
Creating the actual API request uses the “HTTP” premium connector
The formatting of the body ends up looking very confusing as it has lots of escaped characters:
Things to notice here:
- “topics” is the ID of my group. You can use Postman to do a simple boards query and return group ID’s to find the one you want.
- The two blank fields are variables that I’ve initialised and populated earlier in the flow.
- “numbers4” and “people” are two of my actual column IDs so will need changing
- I’m populating two people in the Monday column, hence the two “outputs” fields. These are the outputs from the “Compose” action earlier, within a “personsAndTeams” JSON array. Make sure you put “personsAnd Teams”, both plural, not “personAndTeam” singular.
- The syntax to encapsulate text expressions is a backslash followed by a quote, but these both need to be escaped with another backslash, hence the slightly odd “triple backslash and quote”
I then add another Parse JSON action, using the “body” of the previous HTTP action as the Content and the following Schema:
{
“type”: “object”,
“properties”: {
“data”: {
“type”: “object”,
“properties”: {
“create_item”: {
“type”: “object”,
“properties”: {
“id”: {
“type”: “string”
}
}
}
}
},
“account_id”: {
“type”: “integer”
}
}
}
That gives me the ID of the newly created project, so now I can upload a file (or do whatever)
Add another HTTP action to upload a file:
More things to note:
- A different URL endpoint (adding “/file”)
- “content-type” in the header needs to be “multipart/form-data”
- The body is a different format, as it’s multipart, not raw, and this time doesn’t need the triple-backslash escaping
- “id” is the output of the Parse JSON action which returned the newly created project
- “files” is the ID of the Files column
- “New Demand Form.docx” could easily be replaced with a variable
The variable “MainDocument” was created using the Populate a Microsft Word Template action from the “Word Online (Business)” group:
And then setting the output from this:
Hope someone finds this useful!
- Steve