I'm using an HTTP Action inside an Azure Logic App. I want to send requests to an adress www.example.com with many endpoints (\1, \2 ..).
I don't want to create an HTTP Action for every endpoint, so is there any way to specify all those endpoints in a file and use a kind of lood in that action?
Thank you
Multiples end points
mydomain dot com /Java, /Csharp, / Js
You follow blew steps.
Create array object.
[
{"language":"Java","Book":"P.K Sharma"},
{"language":"CSharp","Book":"S.K Sharma"},
{"language":"JS","Book":"J.K Sharma"}
]
Initialize variable.
Create variable.
For each loop
Add action in for each loop.
Http action
More information on Call, trigger, or nest logic apps by using HTTPS endpoints in Azure Logic Apps by Microsoft Documents.
Related
I have a web app service on azure that is hosting a RESTful api which deals with my MySQL database. I am wondering if its possible to somehow (either manually, or otherwise) upload a page to this app service as well. For instance, i have my URL from azure, and my API lives under /api
I was wondering if i can create a php/html page or something that I can upload to /meetingConfirm
so i can do something like /meetingConfirm?id=hash
And have a page which i can send email links to encoded for each meeting, to allow people to respond to invites. It would be a simple page that just updates a value via the API and then displays a confirmation.
For this, you don't need a separate page to be uploaded for each user. You can just add a multi-threading Id generator code and save the last used Id in your DB for future requests.
I am referring to a solution like this(as I am not sure about your tech stack, sharing python approach): How do you generate random unique identifiers in a multi process and multi thread environment?
I am trying to create a saas and for that, I need to create an API and I am not sure how can I create an endpoint like this https://api.karix.io/message/ here domain is https://api.karix.io and endpoint is the message. I know how to create an API using nodejs but not sure how can I create for the domain-specific.can anyone help me with this problem?
A domain is basically a link to an ip-adress. There are DNS-Servers who transate between the human readable form and the ip.
If you want to run your app on a specific domain you need to purchase that domain (which can be quite costly) and the dns Server will create a link between the domain name and ip adress.
So basically you dont need to do anything in order to create the rest-api for your domain.
Later the request are similiar to this:
https://api.karix.io/message/
http://192.168.111.111:80/message <- The ip obviously differs in production
The name of the domain should be accessible in your request-Object atleast in the express framework.
I am currently trying out Azure Logic Apps and am now trying to create
a first simple flow that acquires data from an external REST API.
I'm using FRED, a hosted Node-Red instance, to create an REST API end-point.
In FRED you use https://x_y.fred.sensetecnic.com/api/hello to access my mock API (where x_y is my user name).
Accessing "https://x_y.fred.sensetecnic.com/api/hello" in a browser returns the intended data as specified in the Node-Red flow. Same thing goes when accessing
"https://x_y.fred.sensetecnic.com/api/hello" using GET in Postman (then adding two required Headers, required by FRED).
The strange thing is that in my Azure Logic App, I am not able to even save the flow with my URI stated as "https://x_y.fred.sensetecnic.com/api/hello". It states "Enter a valid URI". I enter the headers as was required.
So I can get to the REST API directly from a browser or using Postman, but are not able to access it from within an Azure Logic App.
I test the problem is there is a special characters _ in your URI. You could have a try if you delete _ then it won't state error.
So you coudl Initialize a variable to store your name x_y, then insert the variable in the URI. The flow would be like this. If you don't find the name in Dynamic content, you could use variables('name') this expression to insert it.
With this way the GET method will run correctly.
I am created my first aws lambda/serverless app as I want it to scale but perform like an MVC app and blog with many pages. Perfer a tech news site where each article is a separate url as opposed to an AJAX Gmail type of application
Is it possible to do this? I don't want my urls to be mydomain.com/ride.thml but instead to be mydomain.com/pick-up-wild-rydes-unicorn.
Any tutorials besides the aws wild rydes one would be helpful.
I have used cakephp in the past but worry about scaling it horizontally (or any mvc type application).
Thanks.
There's a couple of ways, essentially you need to use the slug as a URL parameter variable.
Create a Hosted Zone for your domain in Route 53
Create an API in API Gateway and put the slug part as a URL Parameter
The routing will probably require a stage directory (e.g. v1) this is ok.
The API will have a generic AWS URL + your stage.
Assign your Route 53 custom domain <your domain> to direct to <API Gateway url>/<stage>/ such that you only need to request <your domain>/<slug>.
Access the {slug} parameter from your Lambda function and serve the appropriate content
Here is my task and may looks very simple. I've two APIs named API-A and API-B. I need to create a Logic App in between these two APIs. API-A should call my Logic App and Logic App should call API-B.
Please help me the steps to do it.
Thanks,
Siva
Yes.
1) Create API App/Web API
2) Deploy API app to Azure or somewhere
3) Get the address of that. For example, http://example.com/api/values is the default.
4) Create Logic App
5) Add HTTP action, with the GET verb, and paste http://example.com/api/values to the URI.
6) Click + below your action and select POST, paste URI and in the BODY field click on the Body button to insert the content from the previous action - it should be there automatically.
Here, in the default API app, the first HTTP action will invoke the GET action of the controller which should return "value1", "value2". Then it send that content to the POST action of the second HTTP action.