Using flows for auto session registrations

Ask the Community Get Answers
1

So I have been trying to work with Knack Support on leveraging Knack Flows for Auto Session Registration. I feel as though I am not really getting anywhere with them via email, and since you cannot talk to them via phone or even screen share, I am pulling out my hair.

Right now, I am handling the auto-registration via custom JavaScript, but I wanted to see if, when “Always Show”(field_187) equals “Yes” in my Sessions table (object_3) that it would then automatically create a registration for the individual for those individuals after they complete the Summit Registration Form (object_1) in the Session Attendance table (object_21).

Accounts (object_6) is then connected to Summit Registrations (object_1) and Session Attendance (object_21) as follows:

  • One Summit Registration record with one Account record (field_165)
  • Many Session Attendance records with one Account record (field_156)

Session Attendee (Object_21) is then connected to Sessions (object_3) via the connection field called Session (field_149)

The instructions that Knack Support gave me to accomplish this are:

  1. Trigger: When a Summit Registration is submitted.
  2. Search for a Single Record: Pull the updated Summit Registration, and get the Account ID from that record.
  3. Search for Multiple Records: Find all existing Session Attendance records linked to that Account (via the Session Attendee field — assuming that’s a connected field).
  4. Search for Multiple Records: Find all Sessions where Always Show = Yes.
  5. Iterator: Loop through each Session from the “Always Show” search.
  6. Router: For each Session in the loop, check if a Session Attendance record already exists for that Session + Account.
       a. If not, create a new Session Attendance record.
       b. If yes, skip it.

I don’t understand step 6, and think I have all other steps set up correctly. When asking for clarification, below was the response I got from Knack Support:

Just to clarify what I meant regarding the Router step:

For each Session in the loop, the router acts as your decision point. It checks whether a Session Attendance record already exists for the current Session + Account combination:

  • If a match is found from your “Search for Multiple Session Attendance Records” step, that means the user is already registered for that session, so you can skip creating a new record.
  • If no match is found, then that’s where you’d create a new Session Attendance record, linking it to both the Account and the Session.

That’s the general logic of how this flow would work based on your setup. Since there are multiple searches, conditions, and possible variations, it’s really important to test this thoroughly on your end to make sure everything is pulling the correct records and creating the intended connections.

This still does not make sense to me.