Connect Jifflenow

Jifflenow runs the 1:1 / expert meetings booked around an event. SYSOI pulls those meetings into the golden record as meeting_held signals — so a meeting attaches to the same person's record as their registration, and feeds sales readiness and the stalled-hot escalation. It's pull-only and metered, run on demand (and on the background sweep).

What you'll need

  • Your Jifflenow company name — the subdomain in your Jifflenow URL

(https://<company>.jifflenow.com).

  • OAuth2 API credentials — a client id and client secret. Create

these in Jifflenow's API/integration settings (or ask your Jifflenow admin).

Connect

  1. In SYSOI, open Connections → Jifflenow → Connect.
  2. Enter your company name, client id, and client secret. The client

secret is stored encrypted at rest and shown redacted.

  1. Save. The card shows Connected.

Map your events

Jifflenow scopes meetings to an event by its event system name. On the connection card, add a mapping: paste the Jifflenow event system name and pick the SYSOI event its meetings should land in. Map as many events as you run.

Pull meetings

From Records for a mapped event, use Refresh Contacts to pull the latest meetings (the background sweep also runs periodically). Each meeting attendee is matched to the golden record by email, so meetings line up with the same people your registration platform (e.g. RainFocus) brought in.

What lands

  • Only external attendees (your prospects / customers) become records — your

own staff (internal attendees) are never created as contacts; the internal host's name rides on the meeting as a note ("who they met with").

  • A meeting where the attendee checked in and didn't no-show becomes a

meeting held (a strong readiness signal); an approved-but-not-yet-held meeting lands as a scheduled meeting.

  • Re-pulling is safe — meetings de-duplicate, so the same meeting never

double-counts.

Verify

After a pull, open a contact who had a meeting and confirm a meeting held engagement appears on their record.

Troubleshooting

  • Auth errors: double-check the company name (subdomain only — not the full

URL) and that the client id/secret are an active Jifflenow API credential.

  • No meetings pulled: confirm the event system name on the mapping

matches the Jifflenow event exactly.