Make Tutorial: Google Sheets to Trello for Beginners
Practise a small Make workflow that turns a new Google Sheets row into a Trello card. Learn field mapping, filters, testing and credit budgeting.

In this guide
- What you will build
- What you need
- 1. Prepare the sample spreadsheet
- 2. Prepare the Trello board
- 3. Add the Google Sheets module in Make
- 4. Add the Trello action
- 5. Add a simple status filter
- 6. Run one test and inspect it
- 7. Choose a schedule that fits your budget
- Common problems
- What to try next
- Sources
This practice project turns a new Google Sheets row into a Trello task card. It gives you a small, visible result to check before you use an automation for everyday business work.
Start with made-up information and manual testing. Once it works, choose a schedule that fits your needs and your Make credit allowance.
Checked November 1, 2026 against Make’s official help and pricing pages. App screens can change. The example below is a practice workflow, rather than a reported customer result.
This lesson is based on official documentation. We have not tested it end to end in a live Make account. Use the checks below to confirm each step in your own practice accounts.
Affiliate disclosure: We may earn a commission if you buy through a provider link on our Make tool page, at no extra cost to you.
What you will build
New spreadsheet row → check its status → create a Trello card.
For example, a row saying “Draft opening-hours post” creates a card in a list called “To review.” You can then decide who should do the task and when.
Make calls this connected workflow a scenario. Each app step is a module. The first module watches the spreadsheet; the second module creates the card.
What you need
- A Make account.
- A Google account where you can create a spreadsheet and connect it to Make.
- A Trello account where you can create a board and list.
- Permission to connect those accounts if they belong to your workplace.
Make’s Free plan currently includes 1,000 credits a month and two active scenarios. Other apps have their own plan limits. This lesson starts with manual runs so you can keep the practice small.
If you are still choosing a platform, read the Make vs. Zapier comparison first.
1. Prepare the sample spreadsheet
Create a Google Sheet called Automation Practice. In the first row, enter these column headings:
Swipe the table sideways to see all columns.
| Request ID | Task | Due date | Status |
|---|---|---|---|
| DEMO-001 | Draft opening-hours post | 2026-11-05 | Ready |
You can download the sample spreadsheet as a CSV. In Google Sheets, choose File → Import and select the downloaded file. Use a new practice sheet so you can keep your business data separate.
Use one sample row while learning. The request ID helps you recognise the resulting card and notice an accidental duplicate.
Keep the rows together without a blank row in the middle. Make’s help page says Watch New Rows stops processing later rows when it encounters a blank row.
The due date is plain text in this first exercise. You will put it into the card description, so you do not need to learn date conversion before the first test.
2. Prepare the Trello board
Create a board called Automation Practice and a list called To review. Use this practice board so you can easily recognise the test result.
You will choose that board and list when setting up the Trello module. Keep a browser tab open on the list so you can inspect the card after a run.
3. Add the Google Sheets module in Make
Create a scenario. Search for Google Sheets, then choose Watch New Rows.
Create the Google connection using Make’s normal connection flow. Sign in to the account that owns or can access the practice sheet and review the requested access.
Select the spreadsheet and the correct sheet within it. Set Table contains headers to Yes and use the heading row that contains Request ID, Task, Due date and Status.
For the first test, limit the number of returned rows to one. This makes it easier to see which spreadsheet record becomes which card.
If Make asks where to start watching, choose the sample row for this first practice run. Starting “from now on” can skip a row that was already there before the module began watching.
Leave scheduling off while you build. If you accidentally switch it on, stop the schedule before continuing the setup.
4. Add the Trello action
Add a second module. Search for Trello, then choose Create a Card.
Create the Trello connection using its normal sign-in and permission flow. Select the Automation Practice board and the To review list.
In the card’s name field, insert the Request ID and Task fields from Google Sheets. Do this with Make’s field-selection controls, rather than typing a field name as ordinary text.
For the sample row, the result should be:
DEMO-001 — Draft opening-hours post
In the description field, add “Due date:” followed by the spreadsheet’s Due date field. You can also include “Created from the Automation Practice sheet” to make the source easy to recognise.
5. Add a simple status filter
Add a filter on the connection between the Google Sheets and Trello modules. Set the condition so that Status equals Ready.
This lets you decide which new rows should create cards. A row marked Draft should not reach the Trello action.
Important: Watch New Rows watches newly added rows. Changing an older row from Draft to Ready does not make it a new row. For this exercise, add the row when it is ready to become a task.
If your real process needs to wait for changes to existing rows, choose a different trigger or design. That is a separate project from this first lesson.
6. Run one test and inspect it
Save the scenario, then use Run once. Check that Make finds the intended sample row and sends it through the filter.
Open Trello’s To review list. Confirm that there is one card, its name includes DEMO-001, and the description shows the expected due date.
Look at the run details in Make. The module bubbles show operations and the records passed between steps. Inspect the fields if a card contains the wrong information.
Check the card before repeating a test. Restarting from an earlier row, resetting the trigger’s starting point, or retrying a failed run can create a duplicate.
Next, add DEMO-002 as a new row with Status set to Draft. Run the scenario once and check that the filter prevents a second card.
Then add a fresh DEMO-003 row with Status Ready. Run once and check that it creates the expected card. Do not rely on editing DEMO-002: this trigger is watching new rows.
7. Choose a schedule that fits your budget
Keep using manual runs during practice. Switch to a schedule only when you understand the result and have checked the usage count.
Make Free has a 15-minute minimum scheduled interval. That means 15 minutes is the fastest allowed interval; it does not mean you should select it for every workflow.
For an hourly schedule running all day, a 30-day month contains about 720 checks. Assuming one credit per check and one per created card, 100 new cards would bring the simple estimate to 820 credits.
That estimate leaves some room within the 1,000-credit free allowance, but your other scenarios, tests and retries also use the same allowance. A 31-day month adds more checks.
By comparison, checking every 15 minutes all day means about 2,880 checks in a 30-day month. Under the same assumptions, the checks alone exceed the free allowance.
If a task does not need an immediate response, consider a slower schedule or manual runs. Inspect your actual usage after several days and adjust the schedule accordingly.
Make’s credit rates can vary by feature. AI steps can change the estimate. The official pricing page and your account’s usage screen are the places to check before paying.
Common problems
The new row was not found
Check that you selected the right spreadsheet and sheet. Check the heading row and the trigger’s starting point. Remove any blank row between the headings and your sample records.
The card shows the words “Request ID” instead of DEMO-001
You probably typed a label rather than inserting the previous module’s field. Reopen the Trello module, insert the actual Google Sheets field, and check the next test result.
A row marked Draft created a card
Check the filter field, comparison and value. Make sure it compares the spreadsheet’s Status field to Ready, rather than comparing two pieces of typed text.
An old row changed to Ready but no card appeared
That is outside this trigger’s purpose. Watch New Rows watches new rows. Add a fresh Ready sample row to test this lesson, or build a separate workflow for changes to existing records.
There are duplicate cards
Look at the request IDs and run history before running again. A repeated test or reset starting point can process the same record again. This small practice workflow does not guarantee exactly one card under every failure condition.
The scenario stopped running
Check the connection status, error details, schedule and remaining credits. Fix the cause and inspect the destination before retrying. Make says scenarios stop when the credit allowance is exhausted until credits become available again.
What to try next
Once the two-app workflow works, you could add a step that writes the Trello card’s ID back to the sheet. That can help you track which task was created, but it adds usage and needs another test.
You could also explore AI-assisted task summaries later. First check the data terms, model cost and result quality. Keep human review before any generated text goes to customers.
Use the free tool finder if you want to explore another small task, or read our Make details and Zapier details.
Sources
Official pages checked November 1, 2026:



