Thank you very much for your suggestion @sdefesche .
We are trying to replicate your solution, I don't have much knowledge about HTTP stuff, do you know what am i supposed to put in the Tenant, Audience, Client ID Credential Type and Secret? Or this is not the right way to do it?
It's a shame that we have to go through all this hassle just to get the Hidden Fields.
Hi @dennisb88 and @cjhenrique ,
I apologize for not answering sooner, I must have missed the question.
I'll walk you through our solution step-by-step.
So, we need the 'Response Submission ID' from the initial TypeForm trigger:
Then we build in a delay. That's very important, since it takes some time for the data from the response to actually be stored and available to use. I usually build in a one-minute delay.
After that, we use the HTTP connector:
I'm using the Dutch UI, but you'll get the drift.
- For 'Method' choose GET, since we want to retrieve a specific response.
- FOR 'URI' the syntax is https://api.typeform.com/forms/{formID}/responses?included_repsonse_ids={actual responseSubmission ID}
- Then we enter a header with key 'Authorization' and a value of Bearer {API key}. (Let's say the API key you got from TypeForm is 12345, the value would look like this: Bearer 12345.
- You can generate API keys (tokens) under Settings>Profile>Personal Tokens in TypeForm
- TypeForm's Responses API basically covers all of it, you can find it here: https://developer.typeform.com/responses/
That's basically it!
MPA will then return a JSON object in the Dynamic Data under the HTTP connector ('Body'), which you will have to Parse using the 'Parse JSON' action. The schema depends on the contents of your actual TypeForm, but can be obtained by running the flow as a test. You can then copy-paste the actual JSON into the 'Parse JSON' connector. MPA will then correctly parse the code into usable items.
In order to get the hidden fields, we will need the item called 'hidden'.
In order to make it work, we then need to also parse this object, using the same method as above. So, we use the 'Parse JSON' action on the 'hidden' object. Then we end up with the actual values of the hidden field available for further use:
It's quite a dense process, but it does deliver.
I hope this helps, let me know if you need more info.
One of the processes we run using this method looks like this:
In one of our flows, we use two hidden fields, a SharePoint id and a first name.
The actual JSON object looks as follows:
I've ran the flow once to generate this schema, then use it as an example load in the 'Parse JSON' connector:
{
"type": "object",
"properties": {
"type": {
"type": "string"
},
"properties": {
"type": "object",
"properties": {
"id": {
"type": "object",
"properties": {
"type": {
"type": "string"
}
}
},
"vn": {
"type": "object",
"properties": {
"type": {
"type": "string"
}
}
}
}
}
}
}Both these values are then available as dynamic data in the rest of the flow:
Does that help?
Hi @sdefesche ,
I can get the value of the response. Thank you.
Only one this that's still strange, that I get the last 25 responses back from my http request..
I don't know why, but I've exactly done as you described:
After the test run, you see that there are 25 results, that's not what we need, we need only the last response.
Do you know why that's happens?
Helpful resources
Power Automate News & Announcements
Keep up to date with current events and community announcements in the Power Automate community.
Community Calls Conversations
A great place where you can stay up to date with community calls and interact with the speakers.
