DOCUMENT OPS

Signed PDF Signature Ledger With Postgres Audit Trail

On each signed PDF in Google Drive, it extracts signer, date, and cert details and writes a normalized verification record to a Postgres audit ledger.

CategoryDocument Ops
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew signed PDF in Google Drive folderGoogle DriveGoogle Drive
  • ActionDownload file and extract signature fieldsShell
  • LogicCompute per-field validation status
  • ActionInsert verification record into Postgres ledgerPostgreSQLPostgres
  • OutputWrite flagged audit row for any failed fieldPostgreSQLPostgres

What it does

Turns every incoming signed PDF into a queryable audit record. It extracts the signer identity, signing timestamp, and certificate issuer/expiry, normalizes them, and inserts a row into a Postgres ledger table with a pass/fail status per field so you have a permanent, searchable trail.

When to use it

Use it when auditors or regulators require proof of when each document was signed and by whom, and you need that history in a database rather than scattered across files. Ideal for finance and compliance archives.

How it works

  1. 1A new file in the Google Drive signed folder triggers the run.
  2. 2The file content is downloaded and a shell step extracts signer, date, issuer, and expiry.
  3. 3A logic step computes per-field pass/fail (signer present, date sane, cert unexpired).
  4. 4An insert writes the document id, fields, statuses, and run timestamp to the Postgres ledger.
  5. 5If any field failed, a flagged row plus reason is written so it surfaces in audit queries.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google DriveDocs, sheets, slides, files.
  2. 2
    Connect ShellRun sandboxed commands inside the workspace.
  3. 3
    Connect PostgresAny Postgres URL — query, write, migrate.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.