When rejected document in Scrive, sync it to Google Forms (Legacy).

When a document is rejected in Scrive, sync the record details to Google Forms (Legacy).

Try:

See all Scrive + Google Forms (Legacy) integrations or talk to a human

Trusted by teams already building on Knit·

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.

Scrive Explore Scrive →

Triggers

Envelope sent

Fires when a document is sent for signature in Scrive.

Envelope signed

Fires when all parties have signed a document in Scrive.

Envelope declined

Fires when a signer declines to sign in Scrive.

Envelope voided

Fires when a pending envelope in Scrive is voided.

Actions

Send envelope for signature

Sends a document out for signature via Scrive.

Void envelope

Voids a pending envelope in Scrive.

Get envelope status

Checks a document's signing status in Scrive.

Create template

Creates a reusable signing template in Scrive.

Google Forms (Legacy) Explore Google Forms (Legacy) →

Triggers

New form response

Fires when a form is submitted in Google Forms (Legacy).

Survey completed

Fires when a respondent finishes a survey in Google Forms (Legacy).

Response updated

Fires when an existing response is edited in Google Forms (Legacy).

Actions

Create or update form

Creates or updates a form or survey in Google Forms (Legacy).

Retrieve a response

Looks up a specific form response in Google Forms (Legacy).

Add a respondent

Adds a respondent or contact to a form in Google Forms (Legacy).

Send signature requests upon form completion When a user completes an intake or agreement form in Google Forms (Legacy), automatically generate and send an envelope for signature using Scrive. See details

Mark respondent status as completed when documents are signed When an envelope is fully signed in Scrive, automatically update the matching respondent profile in Google Forms (Legacy) to reflect completed compliance. See details

Update survey records when a document signature is declined If a client declines to sign an envelope in Scrive, automatically update their survey record in Google Forms (Legacy) so team members can address objections. See details

See all Scrive + Google Forms (Legacy) integrations → · Browse the full workflow library →

Enterprise-grade security

Visit our Security Center Review the DPA

FAQ

Common questions

Can Knit build “When rejected document in Scrive, sync it to Google Forms (Legacy).” between Scrive and Google Forms (Legacy)?

Yes — describe it in the box above and Knit's Integrations Agent researches Scrive and Google Forms (Legacy)'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 Scrive to Google Forms (Legacy) speed up document collection?

When prospective clients or recruits complete an intake form in Google Forms (Legacy), you can automatically send them a personalized signature envelope through Scrive.

Can document signing events update my survey records?

Yes, once an envelope is completed, voided, or declined in Scrive, the corresponding respondent record in Google Forms (Legacy) can be updated automatically.