Found something off? Report it here. This helps us fix issues faster during the Briedo pilot.
← Documentation

Connect your sources

Google Forms

A recipe, not a connection: relay a Google Form with a short script.

What it does

someone submits your Google Form
        ↓
a script on the form signs the answers
        ↓
     Briedo’s signed webhook
        ↓
   a piece of work, with their answers on it

What Briedo reads

The answers your script chooses to send. The form itself is never read by Briedo.

What Briedo may write

Nothing.

Permissions you are granting

None to Google. The script runs inside your own form and holds the Briedo secret. Keep it in the script’s properties rather than in the code.

How to connect

  1. Create an inbound connection in Briedo — Settings, Integrations, Before discovery. Copy the address and the secret.
  2. State that the connection is "A form people fill in". This is what lets the answers count as the client’s own.
  3. In your Google Form, open Apps Script and add an on-submit trigger.
  4. In the script, store the secret as a script property. Do not paste it into the code.
  5. Send each submission to the address, signed, using Google’s own response identifier as the submission identifier.

How to route work

Send Google’s own response identifier as the submission identifier. If the script retries — and Apps Script does — the same identifier tells Briedo it is the same submission, so a retry does not create a second piece of work.

How mapping works

Your script names each Briedo item and gives it the answer. Plain answers are text, numbers or yes/no.

Where your setup expects something with parts — an address as a street, a town and a country — send the parts. A single line of text is refused for that item, and the item stays open. That is the intended outcome: a spreadsheet-shaped address is not an address.

How to test it

  1. Submit the form yourself.
  2. Check the script’s execution log for a success response.
  3. Confirm one piece of work appeared with your answers on it.
  4. Re-run the same execution and confirm no second piece of work appears.

How to know it is working

  • Every submission produces exactly one piece of work.
  • The answers are attributed to the form.
  • Nobody is re-asked what the form already collected.

When it goes wrong

What you seeWhat it means
Signature rejectedThe script signed a different string from the one it sent. Sign the exact body.
Timestamp rejectedSeconds, not milliseconds.
Two pieces of work per submissionThe script generated a fresh identifier on retry instead of reusing Google’s.
Work created but nothing settledThe connection has not been told what it relays.

How to disconnect

Remove the trigger from the form, then revoke the connection in Briedo.

What happens to what it already told us

Nothing is deleted. Work that was already prepared keeps everything it learned, including the record that this system is where it came from. Those are records of what was true at the time, and disconnecting a system later does not make them untrue.

What stops is new information arriving. Deleting historical data is a separate request, and a deliberate one.

Something else?

All guides →