The Zapier app is published at
zapier.com/apps/goliathdata.
You connect your Goliath account to Zapier through the standard OAuth
popup — no API keys to manage.
What you can do
Triggers
Start a Zap when a contact in Goliath gets a new tag.
Actions
Create, update, and find contacts from any other Zapier app.
Authentication
OAuth 2.0 — connect once, no token management.
Capability matrix
| Capability | Direction | Supported |
|---|---|---|
| Contact tag added | Goliath → Zap | ✅ |
| Create contact (structured) | Zap → Goliath | ✅ |
| Create contact from text | Zap → Goliath | ✅ |
| Update contact | Zap → Goliath | ✅ |
| Find contact | Zap → Goliath | ✅ |
| Property / deal events | Goliath → Zap | ❌ (not yet) |
| Note / task creation | Zap → Goliath | ❌ (use update) |
How it works at a glance
- Actions are simple HTTPS calls. Zapier sends a JSON body to a Goliath
endpoint with your OAuth token in the
Authorizationheader. Goliath acknowledges immediately and processes the contact asynchronously. - Triggers are REST hooks. When you turn on a Zap, Zapier asks Goliath to
subscribe a webhook URL. Goliath stores the subscription and fires a
POSTto that URL whenever a matching event happens.
Connect Goliath to Zapier
- From inside Goliath, open Settings → Integrations and click Connect Zapier. This opens the Goliath app on Zapier.
- In Zapier, click Connect a new account on any Goliath trigger or action.
- The OAuth popup will ask you to authorize Zapier to access your Goliath workspace. Approve it.
- You’re done — Zapier remembers the connection for every future Zap.
Where contacts created via Zapier show up
Any contact created through a Zapier action is tagged withSource: Zapier
in Goliath. You can filter your contact list by source to see everything
that has come in via Zapier in the last 30 days from
Automations → Integrations.
Limits & quotas
- Subscription lifetime: Trigger subscriptions auto-expire after 14 days. Zapier renews them automatically while a Zap is on; if a Zap is paused for more than two weeks the subscription is cleaned up.
- Idempotency: Duplicate contact-create requests with identical payloads are deduplicated server-side, so retrying a Zap step is safe.
- Throughput: There is no per-account rate limit on contact webhooks today, but very large bulk imports should be done via the CSV importer instead of one Zap run per row.