Task · Workflows

Send attendees to Validar

Keep your Validar lead retrieval scanners up to date as tickets are bought, changed and voided.

7 steps · About 6 minutes

Validar reads badges at your stand and hands exhibitors their leads. It works from the people you've sent it, so an attendee has to reach Validar before their badge means anything at the stand. This keeps the two in step with nothing to export.

You'll need your Validar API key and the event GUID Validar uses for this event. Both come from your Validar account manager, so ask them for both at once. Validar issues a key for each event, and you connect each one on that event.

1. Connect your Validar key

   Open the event, then Integrations in its settings. Paste your API key and select Connect.

   Your key stays hidden once it's stored.

   Keep your own copy wherever Validar gave it to you. If you lose it, generate a new one at Validar and paste that instead.

2. Start from the template

   Open Workflows, select New from template and choose Send attendees to Validar.

   Your accountWorkflows

   go.tito.io/acme/admin/workflows

   That creates an ordinary workflow you can edit, already set up to fire when a ticket is bought, changed or voided. It arrives switched off.

   If no event has a Validar key yet, the workflow page says so and points you back to your events, where you can open one and paste its key.

3. Put your event GUID in the address

   Open the workflow and look at what it sends. The address reads https://services.validar.com/Events/YOUR-EVENT-GUID/Registrants.

   Replace YOUR-EVENT-GUID with the GUID Validar gave you for this event, like AE40CB39-AB74-4300-AE77-FFF5430BD0C7, and leave the rest of the address as it is. The switch stays out of reach until you do.

4. Check what the template sends

   The template sends the attendee's first name, last name and email, their ticket type, and a registrantId that is Tito's own id for that ticket. Validar uses registrantId to tell an update from a new person, so leave it as it is unless Validar tells you otherwise.

   Those five come from the ticket itself, so they are filled in for every attendee without you setting anything up.

5. Send an answer to one of your questions

   Validar also has a place for an attendee's company and job title, and the template leaves both empty, because only you know which of your questions holds them.

   Find the Fields list on the action and put qrCompany or qrTitle in an empty Field name. The Value list beside it offers what comes with the ticket, the order, the event and your account. For an answer to one of your own questions, choose Something else…. Then open Write my own template and put {{ ticket.answers.company }} in the box.

   Swap company for that question's Export name, which is on the question's own page. Write a key that has hyphens in it as {{ ticket.answers['job-title'] }} instead.

   To stop sending a field you added here, use the bin icon at the end of its row and confirm on the page it opens.

   Your eventSet upQuestions

   A key that matches no question stops the whole send.

   That attendee doesn't reach Validar at all, rather than arriving with one field empty. The next step is how you catch it before anything is live.

6. Check the preview

   What gets sent appears under the fields and shows the JSON Validar will receive, filled in from one of your recent orders.

   Empty fields underneath lists every row that comes out blank, and names any key no question answers to. Fix those before you go on.

7. Turn it on

   Switch the workflow on. From then on, every ticket bought, changed or voided goes to Validar within a few seconds.

Good to know

• Tickets sold before you turned it on stay where they are. The workflow fires on activity, so it covers what happens next. To bring the earlier ones across, use Catch up on the workflow, or open one attendee and run it for just that person.
• You can run a workflow for one attendee or one order. Open it and select View beside Workflows. That page says what covers it and what it last did, and Run does it again for that one record without waiting for anything to change.
• A failed send is retried after a minute, then five, then thirty, then two hours. If it still can't get through, the run is marked failed and stays in the workflow's own run log with what Validar said.
• A rejected key stops there. If Validar answers that the key is wrong, the same key would get the same answer, so paste a new one in the event's Integrations settings.