Join a Team

Which team? *

First name *

Last name *

Email *

Phone *

Location *

Team Orientation

Your best first step, whichever team you choose. Every 3rd Sunday after service: hear the heart behind why we serve, meet your team and leaders, see your serving zone, and get equipped to start. It's relaxed, it's fun, and kids are looked after.

Next: — I'll be at the next one I'll catch the one after

I'm under 18 (youth signup — we'll collect guardian details next)

✓

You're in!

Someone will get back to you with next steps.

📅 Add to Google Calendar Apple / Outlook (.ics)

What gets recorded (for reporting)

For the web team — routing & reporting

Same mechanics as the current per-team Webflow forms, made dynamic: the team dropdown sets team_name + people_flow_[location] from a lookup table (values already exist as hidden fields on each team page today). New hidden fields: orientation_rsvp_date (auto-set to the chosen 3rd Sunday, ISO format) and signup_type (team / rsvp_only / undecided).

On submission: route to the team's People Flow at "New Interest" (or the Inroads flow for undecided/rsvp-only), and write the "Team Orientation" custom field on the profile with Orientation RSVP – [date] — a custom field, not a note, so it's filterable in Lists (this replaces the current note-writing approach). Reporting = filter people by that tag per date/location; after each orientation, compare against the Orientation Completed attendance tag for the no-show follow-up list. Dates need no maintenance — always computed as the 3rd Sunday.

Reminder email: scheduled n8n job runs Thursdays — 3 days before each orientation, it emails everyone tagged Orientation RSVP – [that Sunday] with time, location, what to expect, and kids info. Calendar: the success screen offers Google Calendar + .ics with a built-in 3-day reminder alarm; start times per location are placeholders (Hamilton 11:45, Downtown/Midtown 12:30) — confirm per campus.