I am trying to create custom webhook trigger in Microsoft Flow.
I have created one sample application where I have implemented webhook service. The application calls the hooks when events occur.
I tried integrating my webhook server with Microsoft Flow by referring to link
I created swagger and adding trigger from flow UI but I end-up getting the below error
"InvalidTemplate. Unable to process template language expressions for trigger 'When_File_get_created_in_project_share' at line '1' and column '4703': 'The template language function 'ListCallbackUrl' is not supported by triggers of type 'ApiConnection'.'."
Please help.
Related
I need to know what am I doing wrong with my integration. I will explain first our main goal.
We need to detect new synced projects or created projects on Everhour API using a webhook.
Use that webhook to trigger automation on Zapier and do other APIs we need to do.
The process of creating a webhook using their API is like this:
Use the create a webhook endpoint ( link )
Pass the custom webhook(I created on Pipedream with custom header)
The Everhour API requirements say that I need to reply back a custom header of "X-Hook-Secret ":
So far I have created a webhook on Pipedream which you can create a custom header response see reference here:
This is the request body from the Everhour API to create a webhook, I passed in the Pipedream's custom webhook created.
Now, the problem is when I create a new project on Everhour the webhook doesn't get triggered. I don't know if it's because of the custom webhook from Pipedream that I miss something or else others.
Any useful tips will be a huge help.
I want to send dynamic notification through custom activity which I have created in journey builder. I am able to send only static notifications right now.
It is integrated with third party app through which the notifications will be send. I have integrated that using heroku and github. What changes should I make in config.json, activity.js and customActvity.js.
I have followed below site to create this custom activity and also the same github repository which is given there
https://www.vish-sfmc.com/post/new-changes-new-you
Below is the screenshot of error which I am getting after journey execution. Please tell me why I getting this error, if I need to do changes in node js or in marketing cloud.
As part of microsoft integration service. I'm using an azure logic app that should send message to my GMAIL address each time an event is happening in a VM under a specified resource group.
Scenario applied is :
create RG + VM
create blank logic app
add event grid trigger
add condition ......
send email notificiations
(as of the link : article )
But Logic app designer denied to save as I receive the following message :
Failed to save logic app XXXXla01. The operation on workflow 'XXXXla01' cannot be completed because it contains connectors to applications 'azureeventgrid' which are not compatible with the Gmail connector.
When workraround, I find this article that stated some google policies update.
I'm looking now for an alternative to this issue, where I can still use an azure resource that send notifications to my GMAIL address everytime an event is happening to my VM.
Issue with Gmail API was resolved with the procedure : article
Does anybody know how to retrieve data from SAP module using SAP Message Server (Preview) in LogicApp.
I have connected to on premise gateway but not sure how do I call the SAP module from LogicApp. I have tried to google blogs or article for using SAP Message Server (Preview) but couldn't find anything that could explain how can you connect SAP Module with your logic app on azure.
Thanks
Hi Bhavesh we are mainly using two way to connect Logic app to SAP
1) BABI
2) IDOC
Does anybody know how to retrieve data from SAP module using SAP Message Server (Preview) in LogicApp.
You may get the answer from the Azure official document. The following is the snippet from the document.
1.Add the Request/Response trigger, and then select New step.
2.Select Add an action, and then select the SAP connector by typing SAP in the search field:
3.Select SAP Application Server or SAP Message Server, based on your SAP setup. If you don't have an existing connection, you are prompted to create one.
4.Enter a name for your SAP connection
5.The different SAP options are now available. To find your IDOC category, select from the list. Or manually type in the path, and select the HTTP response in the body field:
6.Add the action for creating an HTTP Response. The response message should be from the SAP output
7.Save your logic app. Test it by sending an IDOC through the HTTP trigger URL. After the IDOC is sent, wait for the response from the logic app:
Note:
Current limitations:
Your logic app times out if all steps required for the response don't finish within the request timeout limit. In this scenario, requests might get blocked.
The file picker does not display all the available fields. In this scenario, you can manually add paths.
I wanna build a small workflow using Azure Logic Apps that contains an "Approval" step, which is simply an API call in my own system, similar to office 365 approval connector.
However, from what I found on the internet, the only way to make a long running task in Azure Logic Apps is to use Webhooks.
In Webhooks, I could not set a value to the parameter I created "Bool-Approved".. so, How can I check it later in a condition step?
The other possible solution maybe is to use Swagger to have an "Bool-Approved" parameter. However, it does not support long running action!
What's the possible solution for me?
As you mentioned, the way to do it is to use the Webhook action, and for that you need to implement the Subscribe/Unsubscribe pattern described here. The webhook action will allow you to get any payload (via an HTTP Post) from the instance-based webhook you are subscribing to.
The points below are a summary of this blog post:
https://www.mexia.com.au/correlation-identifier-pattern-on-logic-apps/
To implement the Subscribe/Unsubscribe Webhook pattern you need to consider:
Subscription store: A database to store the unique message Id and the
instance-based callback URL provided by the webhook action.
Subscribe and Start Request Processing API: this is a RESTful API that is in charge of starting the processing of the request and storing the
subscription.
Unsubscribe and Stop Request Processing API: this is another RESTful API that is only going to be called if the webhook action on the main workflow times out. This API is in charge of stopping the processing and deleting the subscription from the store.
Instance-based webhook: this webhook is to be triggered by your own custom approval event. Once triggered, your webhook is in charge of getting the instance-based callback URL from the store and invoking it. After making the call back to the main workflow instance, the subscription is to be deleted. This is the webhook that is in charge of sending the payload you require to the waiting webhook action in your Logic App.
The subsequent actions will be able to use that response body, so you can implement your conditions, etc.
You can follow the blog post mentioned above to see a detailed example and get more details on how to implement it.
make you api return HTTP code 200 if the response if "ok" and 400 if the response is "not ok". This way you can force logic app to behave the way you need it to behave..