Complete AI Mastery Course

{"contentFormat":"slides.v1","completion":{"requireAllSlides":true,"requireQuiz":true},"slides":[{"kind":"title","eyebrow":"Module 5: AI Automation and Workflows","title":"Connecting Apps: Zapier, Make, and API Basics","body":"Learn how no-code platforms connect your tools and the simple ideas behind APIs. You'll understand how to build multi-app workflows, map data between services, and handle cases where no pre-built connector exists.","outcomes":["Explain how Zapier, Make, and n8n connect apps","Map data fields between steps in a workflow","Describe API basics: requests, endpoints, authentication, JSON, rate limits","Use a webhook to receive data from an external app"],"narration":"Welcome to Module 5. In this lesson, we'll explore how no-code platforms like Zapier and Make connect your apps, and demystify the API technology underneath. By the end, you'll be able to build multi-step workflows and handle data mapping with confidence."},{"kind":"content","heading":"How No-Code Platforms Connect Apps","body":"Each platform provides ready-made connectors (also called integrations or apps) — pre-built bridges to popular services. You authenticate once, and the platform handles the technical conversation for you.\n\n- Zapier — organises work as a Zap: one trigger, then a straight line of actions. Ideal for simple, reliable, linear flows. Its strength is the sheer number of connectors and its gentle learning curve.\n- Make — uses a visual scenario canvas of connected bubbles (modules). It shines when you need branching (\"if the message is a complaint, do X; otherwise do Y\"), loops over lists of items, and multi-path logic you can see at a glance.\n- n8n — open-source and self-hostable, so you can run it on your own server. This gives more control over cost and data privacy, and it exposes lower-level building blocks, making it a favourite for technical teams and organisations with compliance needs.\n\nAnalogy: think of these platforms as universal power adapters. Each app has a differently shaped plug (its API), and the platform supplies the adapter so everything fits the same socket — your workflow.","callout":{"variant":"insight","title":"Choosing a Platform","text":"Zapier is best for simple linear workflows; Make excels at complex logic with branching; n8n offers maximum control for teams with privacy or customisation needs."},"narration":"Let's start with the three main no-code platforms. Zapier uses a linear trigger-action model, Make provides a visual canvas for complex logic, and n8n is open-source for self-hosting. Think of them as universal adapters that make different apps' APIs fit together."},{"kind":"content","heading":"Mapping Data Between Apps","body":"The core skill is field mapping: telling the platform which piece of data from an earlier step fills which slot in a later step.\n\n- Earlier steps output named fields — sender, subject, total_amount.\n- Later steps have input slots — a spreadsheet column, a message body, an email field.\n- You drag or select a field into a slot. The platform inserts the value when the workflow runs.\n\nGet mapping right and everything flows; get it wrong and data lands in the wrong place. Testing (from the previous lesson) is how you catch this.","callout":{"variant":"exercise","title":"Try Mapping","text":"In your next workflow, map three fields from a trigger to an action. For example, map 'sender email' to a spreadsheet column and 'subject' to a message body. Run a test to verify."},"narration":"Field mapping is how you tell the platform which data goes where. You drag fields from earlier steps into slots of later steps. Testing ensures the data lands correctly."},{"kind":"content","heading":"API Basics — The Doorway Between Apps","body":"An API — Application Programming Interface — is the set of instructions one program offers so others can use its features. When your no-code tool \"connects to Gmail,\" it is quietly speaking to Gmail's API.\n\nKey ideas, in plain English:\n\n- Request and response. Your workflow sends a request (\"give me new emails,\" \"create this row\"); the app sends back a response (the data, or a success/failure message). It's like ordering from a menu and receiving your dish.\n- Endpoint. A specific address for one capability — e.g. one endpoint to list messages, another to send a message.\n- Authentication. Proof that you're allowed in, usually via an API key (a long secret password) or OAuth (the \"Sign in with Google\" style permission screen). Definition: an API key is a private token that identifies and authorises you — treat it like a password.\n- JSON. The common text format APIs use to exchange data. It looks like labelled pairs: { \"name\": \"Amara\", \"total\": 45.00 }. You rarely write it by hand, but you'll recognise it in test results.\n- Rate limits. Most APIs cap how many requests you can make in a period, to prevent overload. Hitting the limit pauses your workflow until it resets.","table":{"headers":["Concept","Plain English","Example"],"rows":[["Request/Response","Asking for data and getting it back","GET /messages returns a list of emails"],["Endpoint","Specific URL for one action","https://api.gmail.com/v1/users/me/messages"],["Authentication","Proving who you are","API key or OAuth token"],["JSON","Data format with labels and values","{ \"name\": \"Amara\", \"total\": 45.00 }"],["Rate Limit","Max requests per time period","100 requests per minute"]]},"narration":"APIs are how apps talk to each other. Your workflow sends a request to an endpoint, authenticates, and gets a response in JSON format. Rate limits prevent overload. Understanding these basics helps you debug and go beyond pre-built connectors."},{"kind":"content","heading":"When You Go Beyond Ready-Made Connectors","body":"Sometimes a service you use has no pre-built connector. Every platform offers a generic HTTP / Webhook module for this:\n\n- A Webhook is a URL the platform gives you; another app pushes data to it to trigger a workflow. It's the \"call me when something happens\" pattern.\n- A generic HTTP request step lets you call any API directly by filling in the endpoint, method, headers (where the API key goes), and body — no coding, just careful form-filling using the service's documentation.\n\nExample: Receiving data from a form via webhook\n\n1. In Make, add a Webhook trigger. Copy the generated URL.\n2. In your form tool (e.g., Google Forms, Typeform), set the submission URL to that webhook URL.\n3. When someone submits the form, Make receives the data as a trigger. You can then map the form fields into subsequent actions (e.g., add a row to a spreadsheet, send a Slack message).\n\nYou won't need this on day one, but knowing it exists means no service is ever truly off-limits.","callout":{"variant":"tip","title":"Webhook Setup","text":"When setting up a webhook, always test with sample data first. Most platforms provide a way to send a test payload to verify the structure."},"narration":"When a service lacks a pre-built connector, use a webhook or generic HTTP module. A webhook gives you a URL that other apps can push data to, triggering your workflow. This opens up any service with an API."},{"kind":"content","heading":"Real-World Examples","body":"Here are three examples showing how these concepts come together globally:\n\n- A logistics startup in Kenya connects its order form, a mapping service, and a WhatsApp Business tool. When an order arrives, Make branches on the delivery region, calls a courier's API via an HTTP step to book a pickup, then sends the customer a tracking message — three apps stitched into one flow.\n\n- A university research group in Germany uses n8n, self-hosted for data-protection reasons, to pull survey responses through an API, pass each response to an AI step that classifies sentiment, and write the results to an internal database — all without student data leaving their own servers.\n\n- An e-commerce seller in India wires a payment tool to a spreadsheet and an email app in Zapier. A completed payment (the trigger) maps the buyer's name and amount into a ledger row, then sends a receipt — replacing a nightly hour of manual reconciliation.","narration":"Let's see these concepts in action. A Kenyan logistics startup uses Make to branch orders by region and call a courier API. A German research group self-hosts n8n for data privacy. An Indian seller automates payment reconciliation with Zapier."},{"kind":"quiz","heading":"Check Your Understanding","questions":[{"question":"What is the primary role of an API in app connections?","options":["To provide a user interface for the app","To define how apps can request and exchange data","To store data in a database","To generate passwords for users"],"questionId":"cmrf73k88001ppd27f28awlf5"},{"question":"Which platform is best suited for workflows that require branching logic (e.g., different actions based on conditions)?","options":["Zapier","Make","n8n","All are equally good"],"questionId":"cmrf73k88001qpd27laa81nne"},{"question":"What is a webhook?","options":["A type of API key","A URL that receives data pushed from another app to trigger a workflow","A tool for debugging HTTP requests","A database connector"],"questionId":"cmrf73k88001rpd27igzzjpkz"}],"quizId":"qz_cmk7ljast001tg4p8vshiymyb"},{"kind":"summary","heading":"Key Takeaways","takeaways":["No-code platforms like Zapier, Make, and n8n provide pre-built connectors that handle API communication for you.","Field mapping is the skill of connecting data from one step to the input slots of another step.","APIs work via requests to endpoints, with authentication (API key or OAuth), and return data in JSON format.","Rate limits restrict how many requests you can make in a given time period.","When a connector doesn't exist, use webhooks or generic HTTP modules to connect any service with an API.","Real-world examples show these concepts applied globally, from logistics in Kenya to research in Germany and e-commerce in India."],"narration":"To summarise: no-code platforms use connectors to bridge apps via APIs. Field mapping lets you route data correctly. APIs involve requests, endpoints, authentication, JSON, and rate limits. When no connector exists, webhooks or HTTP modules fill the gap. These skills empower you to automate across your entire toolkit."}]}