How-to / Automation
How to plan your first small automation with Make
Start with one repeat task. Test one fake record. Then decide.
Documentation-based Facts checked on official pages Oct 21, 2026. Interface labels can change.
Heads up: if you sign up for Make through our links, we may earn a commission. It costs you nothing, and some tools come with free trials or perks. Read the affiliate disclosure
Who this is for: A small business operator copying the same data between two apps by hand. You will end with: a written workflow plan and one safe test, not a live integration.
Before you begin
- A free Make account.
- Admin access to the two apps you want to connect.
- A sample sheet or form with fake data only.
- A sentence that names the trigger and the result.
Sample input
Trigger: a new row in a test lead sheet.
Fields: lead_id TEST-001, company Example Store, status New. No real emails.
Result: one matching test record in a sandbox destination.
Steps
Write the event in one sentence
“When a new test lead row appears, create a matching test record.” Pick the field that makes each record unique (here, lead_id).
Checkpoint: one trigger and one unique key.
List the required fields
Write down which fields must exist and what happens if one is missing.
Original diagram of step 2, not a screenshot of the product. Checkpoint: a written field map.
Confirm both connectors
Open Make’s integrations directory and each app’s own docs. Check whether the trigger is instant (webhook) or scheduled (polling), and whether either app needs a paid plan for API access.
Original diagram of step 2, not a screenshot of the product. Checkpoint: a source link for every connection.
Build the smallest scenario
Add only the trigger, a filter for required fields, and the destination. Point the destination at a test record or sandbox.
Original diagram of step 3, not a screenshot of the product. Checkpoint: nothing writes to production data.
Run one test and read the log
Run once with the fake row. Open the run history, count credits used, and run it again to check it does not create a duplicate.
Original diagram of step 3, not a screenshot of the product. Checkpoint: one input, one output, no duplicate.
Estimate monthly credits before scheduling
Credits per run × runs per month must fit 1,000 on Free. Remember the free plan’s 15-minute minimum interval.
Original diagram of step 2, not a screenshot of the product. Checkpoint: your estimate fits the plan, with headroom.
What should you have at the end?
A tested one-step scenario plan: trigger, field map, filter, test result, credits per run and a decision on the plan you need.
What if something goes wrong?
- Duplicate records
- Use the unique ID and search before creating.
- Trigger never fires
- Check app permissions and the polling interval.
- Credits run out
- Inspect which modules run on every cycle and filter earlier.
- Connection expired
- Reconnect through the app’s sign-in flow.
Quick verdict
Plan the trigger, the fields and the failure path before you build. Make’s free plan includes 1,000 credits a month, and most actions use 1 credit, so a small test costs little. A connected app may still need its own paid plan.
Best for
- One repeat task between two apps
- People who want a visual builder with branching
Avoid if
- The task touches real customer data before you have tested it
- You need guaranteed instant triggers on the free plan
Product details, plans and pricing
The how-to comes first. Below are the product facts, plan limits and prices, taken from official vendor pages. Each fact shows the date it was checked; vendors change plans, so confirm on the official page before you buy.
What is free, and what are the limits?
| Plan | Access type | Key limits |
|---|---|---|
| Free | Renewing free plan | 1,000 credits a month; minimum schedule interval 15 minutes |
| Core | Paid | From $12/month billed yearly for 10,000 credits; schedules down to 1 minute |
Make’s pricing page (checked Oct 21, 2026) says each module action uses credits, most use 1, error-handler and router modules use none, and unused credits expire at the end of the term. Plan prices checked Oct 13, 2026.
Which plan do you need?
Stay on Free while the scenario is small. Move to Core when you need schedules shorter than 15 minutes or more than 1,000 credits a month.
Alternatives
- Zapier: free plan with 100 tasks a month and two-step Zaps. See Make vs Zapier.
- n8n: workflow automation you can self-host.
Sources
- Make pricing Not affiliate (checked Oct 21, 2026)
- Make integrations Not affiliate (checked Oct 13, 2026)
- Make help center Not affiliate (checked Oct 13, 2026)
Written by Mishal Brands Editorial. Spot something outdated? Send a correction.