> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jobing.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Spreadsheets and automation

> Send new form responses to Google Sheets, Airtable, Notion, Zapier, or your own webhook.

## Google Sheets

Google Sheets adds each new response as a row.

You need:

* the spreadsheet ID from the address between `/d/` and `/edit`;
* the worksheet name, such as `Responses`;
* the questions you want as columns;
* a Google service account JSON credential.

Share the spreadsheet with the service account email before connecting.

<Tip>
  If you do not manage Google Cloud service accounts, ask your Google Workspace administrator or a developer to create the credential and share the sheet.
</Tip>

## Airtable

Airtable creates one record for each new response.

You need:

* the Base ID;
* the table ID or table name;
* a personal access token with access to that base;
* a mapping from Jobing questions to Airtable field names.

Leave a mapping blank when that answer should not be sent.

## Notion

Notion creates a page in a database for each response.

You need:

* the database ID;
* the title property name;
* the Jobing question used as the page title;
* an internal integration token;
* field mappings.

Share the target database with the Notion integration before connecting.

## Zapier

Zapier triggers a Zap through a Catch Hook.

You need:

* the Catch Hook URL from Zapier;
* an event name, usually `form.response.created`.

Use the test response to build later Zap steps.

## Webhook

A webhook sends a signed response event to your own HTTPS endpoint.

You need:

* the destination URL;
* a private signing secret of at least 16 characters;
* an event name.

Your developer should verify the `X-Jobing-Signature` before using the data.

<Warning>
  Webhooks are intended for a system you control. Ask a developer to configure signature verification and safe retry handling.
</Warning>

For every integration, submit a test response and check **Last success** before relying on it.