Google Drive & Sheets

Crove doesn't ship a first-party Google Drive / Sheets connector yet, but the two most common workflows — save every signed PDF to a Drive folder and append each form response to a Sheet row — are fully supported via Zapier (or any incoming webhook tool).

This page walks through both patterns end-to-end.

Save signed PDFs to Google Drive

Goal: When a document is signed by everyone, upload the final signed PDF to a shared Drive folder so the original (minus the audit trail) lives next to the rest of your team's paperwork.

What you'll need

• A Crove API key — create one at Settings > API Keys
• A Zapier account (free tier is fine for low volume)
• A Google account with access to the destination Drive folder

Setup

1. Create the Zap. In Zapier, hit Create Zap and pick the trigger:
   • App: Crove
   • Event: Document Completed
   • Account: paste your API key
2. Find the PDF URL. Crove's Document Completed trigger payload includes a pdfUrl field — a signed, time-limited S3 URL that points at the fully signed PDF. That's what you'll hand to Drive.
3. Upload to Drive.
   • App: Google Drive
   • Event: Upload File
   • File: map the pdfUrl field from step 1
   • File Name: {{documentName}}.pdf (or {{documentName}} — {{completedAt}}.pdf if you want dated copies)
   • Folder: pick a folder, e.g. Signed contracts / 2026
4. Test & turn on.

Tips

• The pdfUrl expires after a short window (typically a few hours). Zapier fetches and uploads immediately, so this is only a problem if you build a manual delayed flow.
• To file by customer, map the folder dynamically using a Path step in Zapier based on a template variable (e.g. the respondent's company name).
• If you want the audit trail PDF instead of the clean document, use the auditPdfUrl field from the same payload.

Append form responses to Google Sheets

Goal: When someone fills out a public form (e.g. an intake questionnaire), add a row to a Sheet with every field they submitted. Good for lightweight CRMs, lead tracking, or just audit logging.

What you'll need

• A published public form URL (created from any template with Share > Public Link)
• A Zapier account
• A Google Sheet with column headers matching your form field names

Setup

1. Create the Zap.
   • App: Crove
   • Event: Document Completed (or Response Submitted if you want partial / in-progress fills too)
2. Map the payload. Each Crove variable appears as a field in the payload. Zapier will auto-detect them after you run a test trigger.
3. Append to Sheet.
   • App: Google Sheets
   • Event: Create Spreadsheet Row
   • Spreadsheet: pick your sheet
   • Worksheet: pick the tab
   • Map each column to the corresponding payload field (e.g. fullName, email, companyName)
4. Test & turn on.

Pre-filling fields for a smoother experience

If you're already collecting some data in another tool (HubSpot, a CRM, etc.), you can use Crove's pre-fill URL parameters to pass values directly into the form. See Sharing > Pre-fill — drop the pre-fill URL wherever you normally send people a form link and the Sheet entry will be cleaner because every submission has the same baseline fields.

Webhooks instead of Zapier

If you'd rather hit Google Apps Script or Cloud Run directly (no Zapier), set up an outgoing webhook:

1. Settings > Webhooks > Add webhook
2. Point it at your Apps Script / Function URL
3. Subscribe to document.completed and/or response.submitted

From Apps Script you can use DriveApp and SpreadsheetApp to do both of the above with zero intermediary cost. See Outgoing Webhooks for the payload format.

What's on the roadmap

A first-party Google connector is on the roadmap for later this year. It'll skip the Zapier step and let you pick a Drive folder or Sheet directly from the template editor. If that's a blocker for you, reply to our onboarding email and we'll loop you into the beta when it's ready.