Update customer records based on updated form details
When a form response is updated in 97Display, automatically update the matching customer details in Blink Payment to keep billing information accurate.
See all 97Display + Blink Payment 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.
97Display Explore 97Display →
TriggersFires when a form is submitted in 97Display.
Fires when a respondent finishes a survey in 97Display.
Fires when an existing response is edited in 97Display.
Creates or updates a form or survey in 97Display.
Looks up a specific form response in 97Display.
Adds a respondent or contact to a form in 97Display.
Blink Payment Explore Blink Payment →
TriggersFires when a new customer is created in Blink Payment.
Fires when a subscription is canceled in Blink Payment.
Fires when a new invoice is generated in Blink Payment.
Fires when a payment attempt fails in Blink Payment.
Creates a new customer in Blink Payment.
Creates a new subscription in Blink Payment.
Cancels an existing subscription in Blink Payment.
Updates a customer's billing details in Blink Payment.
More 97Display + Blink Payment workflows
Create subscribers from sign-up form responses
When a customer submits a registration form in 97Display, automatically create a new customer and subscription profile in Blink Payment.
See details
Send exit surveys when subscriptions are canceled
When a subscription is canceled in Blink Payment, automatically add the customer as a respondent in 97Display to collect exit feedback.
See details
See all 97Display + Blink Payment integrations → · Browse the full workflow library →
Common questions
Can Knit build “Update customer records based on updated form details” between 97Display and Blink Payment?
Yes — describe it in the box above and Knit's Integrations Agent researches 97Display and Blink Payment'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.
How does connecting 97Display and Blink Payment streamline subscription workflows?
Form entries in 97Display can automatically create subscribers in Blink Payment, while subscription changes in Blink Payment can initiate automated survey outreach.
Can survey responses update existing subscriber records?
Yes, when a customer submits or updates information in 97Display, their contact and billing profile in Blink Payment can update automatically.