Flyer Creation with n8n — Simple and Fast

The team activity — a flyer with an embedded n8n form

To make automation feel concrete, learners were grouped into small teams and given one job for the afternoon: produce a real flyer they could share with friends or family, with a working sign-up form built in n8n and embedded in the flyer as a QR code or short link. Every submission would trigger an email to the team's Gmail inbox.

The end-to-end workflow they built has just two nodes:

1. On form submission — n8n's Form Trigger node, configured with the fields the team wanted on the flyer (name, email, message).
2. Send a message — a Gmail node that takes the form values and emails them to the team's inbox the moment someone hits submit.

Two nodes is all it took. Once the workflow is published in n8n, the Form Trigger exposes a public production URL — that is the link teams pasted as a QR code on their flyer. Anyone scanning the QR fills the form, the submission travels through n8n, and a notification email arrives in Gmail within seconds.

The six steps the class followed

This is the exact build sequence Dr. Ang put on the whiteboard. Each step takes only a few minutes once the previous one works.

1. Add the form. Drop in the On form submission trigger node. Name the form, add the fields the flyer is collecting (e.g. Name, Email, Message), and choose which fields are required.
2. Create an email. Add a Gmail Send a message node after the trigger. Connect the team's Gmail account once via OAuth, then map the form fields into the email subject and body using n8n's expression editor.
3. Publish the workflow. Toggle the workflow to Active. This is what tells n8n to start listening on the public form URL — until you publish, the form only works in test mode.
4. Get the production URL from the form. Open the Form Trigger node and copy the Production URL. This is the link real visitors will use — not the test URL.
5. Design a flyer using PowerPoint or Canva. Lay out a simple A5 or A4 flyer with the event name, date, a short benefits line and a clear call to action ("Scan to RSVP").
6. Embed the production URL on the flyer as a QR code. Generate a QR code from the production URL (Canva, PowerPoint and most QR generators do this in one click), drop it on the flyer next to the call-to-action, and print or share digitally. The QR is the bridge between the printed flyer and the audience's phone — scan, fill, submit.

By the end of the afternoon every team had a printable PDF, a working form behind it, and a Gmail inbox quietly collecting test submissions from each other's phones. For most of the seniors this was the first software they had ever shipped to a real audience.

Why the QR code is the heart of the flyer

Anyone can put a URL on a flyer. Almost nobody types it in. A QR code, on the other hand, turns the flyer into a one-tap experience — and that single change is what shifts the audience from reading the flyer to using it. In a community-hall setting it looks like this:

1. Print the flyer with a clearly labelled QR code. Put a short instruction next to it — "Scan to RSVP" or "Scan to sign up". The bigger the QR, the better the scan rate at arm's length.
2. The audience opens their phone camera and points it at the QR. Every iPhone and Android phone made in the last several years recognises QR codes natively — no app, no install. A small banner appears at the top of the screen with the form link.
3. They tap the banner and the n8n form opens in the mobile browser. Because n8n's form is mobile-responsive by default, fields stack vertically and the keyboard surfaces automatically for the first text field.
4. They fill in the form on their phone — name, email, message — and tap submit. The form is short on purpose, so the whole interaction takes well under a minute.
5. n8n triggers the Gmail node and an email lands in the team's inbox within seconds. If the room is quiet enough, you can hear the notification chime go off on the laptop at the front. That instant feedback loop is what makes the demo land.

For the seniors in this class, that final chime was the moment automation stopped being an abstract idea. They had drawn a workflow on a screen, printed a flyer, and watched a phone in someone else's hand cause an email to arrive on their laptop — without writing a single line of code.

Practical tips for a high-scan-rate QR flyer

• Minimum size: 3 cm × 3 cm on print. Smaller QRs work but are unreliable in dim community-hall lighting.
• Quiet zone: leave at least 4 mm of white space around the QR — overlapping graphics break the scan.
• Contrast: dark QR on a light background. Reversed QRs (light on dark) scan inconsistently across phones.
• Label it: a short verb-led instruction next to the QR ("Scan to RSVP") raises scan rates dramatically compared with a bare QR.
• Test before printing: open the camera app on two different phones and confirm the QR resolves to the n8n production URL, not the test URL. Reprinting after a publish-toggle bug is the most common mistake.
• Add a short fallback URL underneath (e.g. a Bitly link) for the small fraction of older phones that cannot read QR natively.

The QR-code-to-Gmail loop is also the simplest demo we know of for showing a non-technical sponsor or executive what n8n can do for their team. If you would like us to run the same demo for your organisation, book a live n8n demo.

What "good" looked like in each team's submission

Build dimension	What we asked for	Why it mattered
Form fields	3 fields max — Name, Email, Message	Long forms kill response rates; the lesson was discipline, not feature creep.
Required vs optional	Email required, the rest optional	You only need one channel to follow up.
Email mapping	Submitter's email and message rendered cleanly in the Gmail body	Teaches n8n expressions in a way that pays off immediately.
Workflow status	Toggle set to Active	The single most common bug: forgetting to publish.
Flyer call-to-action	One QR, one short headline, one date	Forces clarity — the whole flyer should read in under five seconds.

Common stumbles — and the fixes

• "The form opens but nothing happens when I submit." The workflow is still inactive — flip the toggle in the top-right to Active, then test again.
• "I copied the URL but it says 404." The test URL was copied instead of the production URL. Re-open the Form Trigger node and copy the Production URL field specifically.
• "Gmail is asking me to log in every time." The Gmail credential was created but not saved on the node — re-pick the credential from the dropdown after connecting.
• "Submissions arrive but the email body is blank." The expression mapping points at the wrong node output — drag the field from the Form Trigger output panel directly into the Gmail body.
• "My QR code goes to the wrong page." The flyer was generated before the workflow was published, so the QR was made from the test URL. Regenerate after publishing.

Why this format works for adult learners

Building one real artefact end-to-end beats covering ten features superficially. The flyer is a tangible deliverable the learner can hand to a friend or pin on a community noticeboard. The Gmail notification proves the automation is real — a submission from someone else's phone lights up the learner's inbox in front of them. That moment of "I built something that listens to the world" is the entire point of an introductory class, and it sticks in a way that a feature tour never does.

For organisations or community groups who want to run a similar session for their members, we deliver the same one-day format on-site or virtually, scoped around the workflows the group actually wants to automate — RSVP collection, volunteer sign-ups, donation pledges, vendor enquiries. See our AI agent and workflow deployment service, or read our AI agent stack comparison for what sits above n8n once teams outgrow simple automations.

FAQ

Do learners need to install anything on their laptop?

No. The class runs on a hosted n8n instance, so seniors only need a browser. This removes the single biggest barrier to entry for non-technical learners — local installs, Docker, ports — and lets the day stay focused on building.

How is this different from learning Zapier or Make?

n8n is self-hostable and has no per-execution metering on the self-hosted plan, which matters when you graduate from a flyer form to running thousands of submissions per month. It is also AI-native — when learners are ready, the same canvas adds LLM, agent and vector nodes. Zapier is fine for a single integration; n8n is the path if you expect the workflows to keep growing.

What does a learner walk away with at the end of the day?

A working n8n workflow, a published production form URL, a printable flyer PDF with the QR code embedded, and the muscle memory to build the same pattern again for any future event. The Gmail inbox they used during the class continues to receive submissions for as long as the workflow stays active.

Can my organisation book the same class for a private group?

Yes — the format scales from 6 to about 20 learners per session. We tailor the team-activity brief around your organisation's real use cases (RSVPs, donations, volunteer sign-ups, internal request forms) so the artefacts learners leave with are usable from day one.

What is the formal course pathway after this introductory day?

Learners who want to go further enrol in the WSQ Agentic AI Automation with n8n course at Tertiary Courses Singapore, which extends the same canvas into multi-step, AI-powered workflows. For a broader view of related skills, see the AI courses at Tertiary Courses Singapore.

What to do next

1. Read. Skim the AI agent comparison to see where n8n sits in the wider agent stack.
2. Learn. Enrol in the WSQ Agentic AI Automation with n8n public course for the structured pathway.
3. Buy. Request a quote for a private one-day n8n class or a scoped n8n build for your organisation.

Tertiary Infotech Academy delivers public and private n8n training, plus production n8n builds, for Singapore organisations and community groups — talk to us about a tailored programme.