Integrations Overview
Goliath integrations extend your workflow by connecting the tools your team already uses every day. Once connected, email and calendar integrations keep your communication in sync, Slack keeps your team notified in real-time, and Zapier bridges Goliath to thousands of other apps. Each integration unlocks specific capabilities—two-way email sync, calendar availability, real-time notifications, or custom automation—without forcing you to change how your team works. This article explains what each integration does and when to use it; setup steps live in the individual “Connecting X” guides.
Google (Gmail + Google Calendar)
Section titled “Google (Gmail + Google Calendar)”Scope: Per-user—each team member connects their own Google account.
What it unlocks
Section titled “What it unlocks”Two-way email sync. Outbound emails sent from Goliath leave from the user’s real Gmail address, so recipients see the rep’s personal or business email—not a shared service address. Inbound replies from contacts land back in Gmail and are automatically attached to the contact’s timeline in Goliath. Historical email threads with known contacts backfill into the timeline after connection, so you see the full conversation history without manual imports.
Two-way calendar sync. Appointments booked in Goliath create real Google Calendar events, complete with invitees. Events created directly in Google Calendar appear in the Workspace Calendar alongside Goliath-native appointments. This bidirectional sync means rep availability for Forms & Bookings pages respects all their real meetings—not just the ones logged in Goliath—so double-bookings become impossible.
Contacts sync (optional). Google Contacts can be imported so address book entries become Goliath contacts without a CSV upload. This is useful for teams migrating from Gmail-only workflows.
When to use it
Section titled “When to use it”Connect Google if any team member’s primary email and calendar live on Google Workspace or personal Gmail. Each user connects individually, so mixed environments (some on Google, some on Microsoft) are fully supported.
Microsoft (Outlook Mail + Outlook Calendar)
Section titled “Microsoft (Outlook Mail + Outlook Calendar)”Scope: Per-user—each team member connects their own Microsoft 365 or Outlook account.
What it unlocks
Section titled “What it unlocks”Two-way email sync. Equivalent to Google: sends go out from the user’s real Outlook address, inbound replies sync back to the contact timeline, and historical threads with known contacts backfill automatically after connection.
Two-way calendar sync. Equivalent to Google: bidirectional appointment sync and real availability surfaced on booking pages. Appointments created in Goliath appear in Outlook, and Outlook events appear in Goliath’s Workspace Calendar.
When to use it
Section titled “When to use it”Connect Microsoft if any team member’s primary email and calendar live on Microsoft 365 or Outlook. Teams with mixed providers can connect each user to the provider they actually use—no forced standardization required.
Scope: Org-wide—connected once by an admin, used by the whole team.
What it unlocks
Section titled “What it unlocks”Real-time notifications. Slack channels receive instant updates for key Goliath events: new lead submissions from forms, missed calls, new contacts created, deal stage changes, workflow runs completed or failed, and Custom Data Pipeline signal matches. Your team sees activity as it happens, without polling the Goliath UI.
Channel routing. Different event types can target different channels. For example, #new-leads receives form submissions, #deals-pipeline receives stage changes, and #oncall receives missed calls and David AI handoffs. This keeps each channel focused on the events that matter to that team.
Destination for pipeline alerts. Slack is the most common webhook target for Custom Data Pipelines, so ops teams can react to new property signals the moment they arrive—whether that’s a distressed owner listing, a tax delinquency update, or a new permit filing.
When to use it
Section titled “When to use it”Connect Slack if your team already lives in Slack and wants real-time visibility into lead and deal activity. Slack is especially valuable for distributed teams where not everyone monitors the Goliath UI continuously.
Zapier
Section titled “Zapier”Scope: Org or per-user (uses an API key; scope depends on who creates the Zap).
What it unlocks
Section titled “What it unlocks”Goliath-as-trigger. Zapier can listen for Goliath events—contact created, deal moved, tag added, property signal received, workflow run—and fire downstream Zaps in thousands of other apps. Common uses include logging every new lead to a Google Sheet or Airtable for ad-hoc reporting, pushing contacts into a direct-mail provider like Lob, enriching leads via a dialer or data-append tool, and syncing new deals to Notion or a finance spreadsheet.
Goliath-as-action. Zapier can create contacts, update deals, add tags, and trigger workflows from external events. For example, a form submission on a non-Goliath landing page creates a contact via Zapier, a Stripe payment triggers a deal stage move, or an inbound email in Zendesk creates a Goliath contact automatically.
When to use it
Section titled “When to use it”Use Zapier for any integration Goliath does not ship natively. Zapier is the escape hatch: if your team needs Tool X and it does not appear in the individual “Connecting X” articles, Zapier is almost certainly the bridge. For inbound data from external websites via scraping and webhooks, Custom Data Pipelines (covered in a separate article) are the companion path—Zapier handles inbound and outbound via other apps’ APIs, while Custom Data Pipelines handle inbound from sites with no API.
Choosing the Right Integration
Section titled “Choosing the Right Integration”Communication: Connect Google or Microsoft depending on what each team member uses. If users are on different providers, each connects their own—no org-wide choice is needed.
Real-time team visibility: Add Slack so the team sees lead and deal activity in chat, without manually checking Goliath.
Custom workflows with other apps: Use Zapier for API-based integrations with external tools. Use Custom Data Pipelines for scraping-based workflows when the source has no API.
Frequently Asked Questions
Section titled “Frequently Asked Questions”Q: Do I need to connect both Google and Microsoft?
Section titled “Q: Do I need to connect both Google and Microsoft?”No. Connect only the provider each user actually uses. If your team is mixed—some on Gmail, some on Outlook—each person connects their own account. Goliath does not force a single email provider across the org.
Q: Can two users share one connected inbox?
Section titled “Q: Can two users share one connected inbox?”No. Each integration is tied to one user account. If two reps share a Gmail address in real life, only one can connect it in Goliath. Best practice is to give each rep their own email account and connect individually.
Q: What data persists if I disconnect an integration?
Section titled “Q: What data persists if I disconnect an integration?”Everything already synced stays in Goliath—emails on contact timelines, calendar events, imported contacts, and Slack messages already sent. Nothing new flows until you reconnect, but historical data is not deleted.
Q: Are there per-plan limits on integrations?
Section titled “Q: Are there per-plan limits on integrations?”Some integrations are tiered by plan. Zapier and Custom Data Pipelines often live on higher-tier plans. Email, calendar, and Slack are typically available on all plans, but check your billing settings or contact support to confirm which integrations your plan includes.