When attendee checked in in OBVIO, sync it to Adobe Acrobat Sign.
When an attendee checks in in OBVIO, send a waiver document for signature via Adobe Acrobat Sign.
See all OBVIO + Adobe Acrobat Sign integrations or talk to a human
4.9/5 on G2·
Google for Startups Accelerator
How Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
OBVIO Explore OBVIO →
TriggersFires when someone registers for an event in OBVIO.
Fires when a new ticket order is placed in OBVIO.
Fires when an attendee checks in at an OBVIO event.
Fires when an event in OBVIO is canceled.
Creates a new event in OBVIO.
Registers an attendee for an event in OBVIO.
Updates an attendee's details in OBVIO.
Creates or updates a contact in OBVIO.
Adobe Acrobat Sign Explore Adobe Acrobat Sign →
TriggersFires when a document is sent for signature in Adobe Acrobat Sign.
Fires when all parties have signed a document in Adobe Acrobat Sign.
Fires when a signer declines to sign in Adobe Acrobat Sign.
Fires when a pending envelope in Adobe Acrobat Sign is voided.
Sends a document out for signature via Adobe Acrobat Sign.
Voids a pending envelope in Adobe Acrobat Sign.
Checks a document's signing status in Adobe Acrobat Sign.
Creates a reusable signing template in Adobe Acrobat Sign.
Common questions
Can Knit build “When attendee checked in in OBVIO, sync it to Adobe Acrobat Sign.” between OBVIO and Adobe Acrobat Sign?
Yes — describe it in the box above and Knit's Integrations Agent researches OBVIO and Adobe Acrobat Sign's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.