Automation for clients

Stage 2 · Lesson 6 of 7

Connections, webhooks and the HTTP app

Make in depth

Make stores your access to each app as a . You create it once, through OAuth or an API key, and modules reuse it. For apps without a ready-made module, the HTTP app can send any .

It has its own options for API keys, (a username and password) and OAuth 2.0. Custom webhooks work the other way round: they receive data from any app that can send it. Make can also define a , so incoming JSON is split into fields you can map.

Paid plans add the Code app, which runs or Python and charges credits for its execution time. Together these let you connect the unusual apps clients rely on.

Common trapbuilding on a personal Google connection for a client workflow, which breaks when you leave or lose access.

A question to check yourself, an AI practice session and 2 cheat sheet entries come with the full roadmap. Unlock

Resources for this stage

Start with

  • CourseFree
    Make Academy

    Make · Beginner

    Free official courses from Foundation to Advanced, with badges and a certification

Keep handy

  • Official pages on modules, mapping functions, routers, iterators and credits

Mark this stage as not done?