#83 · How Broke Beginners Are Winning With AI Agencies
You can still add one; it's pretty foundational. Just use the Typeform 'Watch Responses' module, which has webhook functionality built in, so you don't need a separate webhook.
There is no webhook on the Upwork scraper in Maker School. I'm not really sure what you're referring to. You're referring to the HTTP request. You have to call the automation page, though there have been some issues. I don't recommend using my own scraper; I use Upwork. The Upwork extractor is good, and the Upwork scraper without stale job posts works well. The most popular scraper is now rated poorly, so try the newer ones—they're more reliable. Cloud Genius is the next option.
There's no built‑in way to turn a polling trigger into an instant one in Make.com. First, check if the service offers a webhook alternative; if so, use that webhook instead of the polling trigger. If no webhook exists, you’re stuck with polling for now, though it’s inefficient and will likely be replaced by webhook‑based systems in the future.
Normally you create the automation inside the Scenario Builder, then schedule a kickoff call with the client. During the call you walk them through signing up for a Make.com account, often sharing your screen and guiding them step‑by‑step. Once they have their own Make.com environment, you can build the automation directly in that workspace. When the automation is ready, you deliver it within their environment, completing the hand‑off and turning the lead into an official client.
The weight (actually wait) node in Make simply pauses the scenario for a set amount of time; it isn’t a webhook. The webhook URL is generated at runtime and the scenario resumes when the webhook is called. You can define a callback URL in Appify so that when the Upwork actor finishes it calls that webhook and the flow continues. In the example Santi uses n8.pulsense.com/webhook as the callback. There’s also a newer Appify API endpoint that runs the actor synchronously and returns the data set items directly, eliminating the need for the wait‑node‑plus‑webhook pattern. Using that endpoint is the simpler, more reliable way to avoid delays or missed updates.