Make.com
Last updated
Last updated
Once you have signed in to , click the button to get started working on your workflow. Note that you need to have a working TextLink account, and follw the in order to be able to actually use TextLink.
Congratulations! You have completed the trigger setup. You can now easily use the Webhook data in next steps.
As mentioned earlier, you can specify a secret in your Webhook configuration (step 4). Only you and our server knows that secret. You can confirm that the request is coming from our server by adding the Router component at the beginning of your workflow, as shown below.
Click the dots between the router element and the next element (1st) to set up your filter. Enter any label. For condition, configure it so it checks whether the secret field provided in the webhook is your webhook secret, pasted from the step 4 in webhook creation.
For Body type, select Raw. For Content type, select JSON (application/json). For request content, you need to use this base form (you need to specify other fields based on the API endpoint specification):
And you can then reuse all the other fields in your workflow by clicking them in the pop-up menu to the right. You can see that we are sending "Hello there" to the phone number from the trigger Webhook.
That's it! You can trigger other API endpoints similar way.
In this tutorial, you will learn how to create a trigger for receiving SMS, but other triggers can be done identically. For list of other triggers, check the page.
Select Webhooks as the trigger for your workflow
And then choose Custom webhook
Create a new webhook, give it a name (anything you want), and click Save.
Click the Copy address to clipboard button:
Go to ("API & Hooks" page), and paste the copied URL into the input for the action that you would like to use to trigger your webhook (in our case Receive SMS action). Also if you have not set a webhook secret, click the Generate button next to the webhook secret. That secret is only known to you and our servers, and you can use it to authorize requests if needed.
Click Save and then Test webhooks. If everything is working, you should get the following confirmation:
Go back to Make.com, and click the Save button (can also be called Ok). You should now see the test request. Click Continue with selected record
Click + to add a new component to your workflow. Select a router
Now you can see that it created two branches. We are safe to ignore the request if the secret is invalid, so we can delete the second branch by right clicking on it:
You can call any endpoint defined on the from Make. This example shows how to create a send SMS action. To get started, click the + button to add an action after your webhook or your filter (as seen in previous step).
Select the HTTP App
Select Make a request action
Fill out the URL, Method and Headers using the specification of the API call that you want to use (send-sms in our example). Make sure that the vaule of the Authorization header is Bearer YOUR_API_KEY, where you can find your API key in .
