Connect your stack

Google Sheets

1. Connect Google Sheets in Integrations. This is a separate grant from Gmail and Calendar.
2. Choose Manage lists, select a saved list and use Choose Google Sheet with the same Google account. The picker grants access to the file you choose.
3. Save the list connection, then Push list. Guffles creates one managed tab for that list with stable record keys and prepared columns.
4. Use columns to the right for your own data. Keep keys, headers and owned columns intact. Avoid editing owned cells while a push is running and sort complete rows when needed.

Consent uses basic identity and drive.file, covering files you select. Cells above 50,000 characters pause; managed tabs retain up to 29,000 tagged records. Your Google file access and quotas apply. Google scope reference.

Airtable

1. Connect Airtable and grant access to the bases you want Guffles to use.
2. Create a single line text field named Guffles Key in your destination table. Keep those keys intact. The app reads schema; it does not create your fields.
3. Choose Manage lists, select a base and table, choose the key field and map prepared values to writable fields. Use plain long text for drafts and complete JSON values.
4. Save, then Push list. Native upsert follows the stable key. Unmapped fields stay intact. Automatic sync is optional.

The grant requests record read/write and base schema read. Computed and rich-text fields are excluded. Airtable quotas, base access and 100,000-character text limits still apply. Guffles retries rate limits and pauses mappings that need attention.

Salesforce

Connect Salesforce from Settings, Integrations. Your Salesforce administrator may need to approve the Guffles app and enable API access for your account.

1. Have your Salesforce admin review and deploy the Guffles field metadata. It includes fields for Lead and Contact, field permissions and the immutable-key validation rule. Deploy it separately from the OAuth package so the field names stay unnamespaced.
2. The connecting user needs API access and read/create/edit permissions for the chosen object and mapped fields. Connect production or sandbox explicitly.
3. Choose Leads or Contacts in Manage lists. Use prepared field mapping, then review required values. Lead requires LastName and Company; Contact requires LastName and any additional fields your org requires. Choose your own constant when a required source value is missing.
4. Email matching is off by default. Enable it only if you want to adopt a unique visible record with a blank Guffles key. Your admin must retain the supplied key rule and allow read-only rule verification with View Setup and Configuration.
5. Save and push. Keys contain the workspace identity and lead ID. Duplicate matches, foreign keys, field limits or org rules pause instead of silently overwriting a different workspace's record.

Scopes: api refresh_token id. No Accounts are created. Converted Leads, org validation rules, API-enabled editions and provider quotas can affect writes. Salesforce app setup reference.

Zapier

Use the workspace API in your Zapier HTTP actions. Create a scoped key in Settings and choose an endpoint from the developer docs. A webhook receiver must verify the original signed bytes; polling the API is also supported.

Create a workspace API key in Settings with the permissions your Zap needs, then use that key to connect Guffles. The Guffles Zapier app uses signed REST-hook notifications for lead, list and completed-job events. Actions read leads, manage lists, start searches and verification/enrichment jobs, and export prepared data.

Triggers contain IDs, status and counts. Use API reads, or the app's Get Lead and job actions, for full data. Jobs return queued status and use the same credit rules as the dashboard. For retries of a single action, preserve its request ID. Zapier task pricing and delivery delays depend on your Zapier plan.

n8n core node templates

Download an inactive workflow, then import it into a supported n8n release. These use core nodes; no community package is required. Node versions were checked against n8n 2.41.6. Your n8n hosting or subscription is separate.

1. Create an HTTP Header Auth credential named Guffles workspace API key. Set Authorization to Bearer YOUR_GUFFLES_KEY, then select it on every HTTP Request node. Keys belong in credentials, not workflow JSON.
2. Replace host, list/lead, endpoint and stable-request-ID placeholders. Reuse the ID for retries of the same input; use a new ID for new work.
3. For hooks, replace the path with a random UUID and register the production HTTPS URL in Guffles. Keep Raw Body enabled, pass the original binary data and all three X-Guffles delivery headers into Verify original bytes.
4. Read the verified event response. Put your destination before Respond to Webhook and make effects idempotent with the event ID. A test ping is acknowledged without running an export or a paid job.
5. Disable storing successful or failed execution data containing contacts, binary CSV or credentials. Finish setup before activating the workflow. Poll a started job or use its completion event to obtain terminal status.

Customer API and signed webhooks

Read the API and OpenAPI docs. Create, list and revoke workspace keys in Settings. Keys are shown once, stored hashed and limited to the permissions you choose. Cookie sessions do not authenticate the API.

Manage HTTPS endpoints and event types in Integrations. Verify timestamped HMAC signatures over original bytes, deduplicate by event ID, and fetch full data through the authenticated API. Guffles retries eight attempts and disables an endpoint after ten consecutive exhausted deliveries. Use its delivery log, redelivery and test ping controls.

Private/internal receivers are blocked. API limits and credit reservations apply to all plans, including trial. Future outreach event names are reserved; they cannot be selected until those producers exist.

HubSpot

Connect your HubSpot portal in Integrations, then use Push leads. The existing durable sync creates Guffles prepared properties and shows confirmed progress. Reconnect if the grant needs the property scopes. Your HubSpot permissions and quotas apply. Removed Guffles leads leave remote contacts intact.

Gmail and Calendar

Use Manage mailboxes for the existing Gmail and Calendar connection, including the sending-responsibility acknowledgement. Sheets uses a separate client and grant. A Sheets connection does not grant Gmail or Calendar access.