Integrations

Everyone signs in to Verbial with their Google Workspace account; there are no passwords to manage.

• Sign-in is Google only. A person joins by being invited on their work email and signing in with that Google account.
• Removing someone from your Google Workspace ends their access at the next sign-in.
• Client portal access uses its own emailed access codes and does not require a Google account.

Setup guide

Each rep connects their own Gmail so email with CRM contacts is logged in both directions without BCC addresses.

• A sync every five minutes logs mail exchanged with a CRM contact on that contact's timeline, sent and received, aliases included.
• Sequences and one-off CRM emails can send from the connected Gmail so replies land in the rep's inbox.
• Replies to a logged email stop the sequence the contact is enrolled in.
• Mail with no contact match, internal mail and anything under a no-log rule is skipped entirely. A Gmail label named "No log" excludes a message from the inbox.
• Sent mail to an unknown address can create the contact and company; received mail never does.

CRM · Setup guide

Proposals, invoices, receipts, notifications and CRM sequences go out through Postmark from your own sending domain.

• Each brand sets its own from name and address, so a client sees mail from your agency, not from Verbial.
• Bounces and spam complaints come back through the Postmark webhook and suppress the address.
• Replies to a CRM email are parsed by Postmark inbound, recorded on the contact and stop any running sequence.
• Open tracking and a separate marketing stream are supported for sequences.

Setup guide

Booking links check free/busy across every Google account a rep connects and create a Google Meet event for each booking.

• A rep can connect several Google accounts; every calendar each account can write to counts, so a meeting on either blocks the slot.
• Scopes are limited to free/busy, the list of calendar names and creating events on calendars the rep owns. Verbial never reads event titles, attendees or bodies.
• Each booking creates a calendar event with a Google Meet link and sends reminders.

CRM · Setup guide

Card payments on invoices are recorded against the invoice with the Stripe payment reference, so payouts reconcile to open invoices.

• Record a card payment on any invoice with its Stripe payment id; the invoice moves to paid and the payment shows on the client's statement.
• Payments are recorded gross; processor fees are booked in your accounting system, not netted off the invoice.
• Paid invoices are mirrored to the accounting bridge (see QuickBooks Online).
• Your Verbial subscription itself is billed through Stripe.

Invoicing · Setup guide

Clients pay invoices by wire or ACH using the bank details on the invoice, then submit the reference for your bookkeeper to confirm.

• Bank details and payment instructions are set per brand and printed on every invoice and its PDF.
• The client submits the wire reference from the public invoice page; the payment stays pending until someone with the bookkeeper role confirms it landed.
• One deposit covering several invoices is recorded as one payment per invoice with the same posted date.

Invoicing

Clients can pay invoices and proposal deposits in USDC or USDT to the wallet address on the invoice.

• Wallet addresses are configured per brand and shown on the invoice and the proposal checkout page.
• The client submits the transaction id; the payment is pending until someone with the bookkeeper role verifies it on chain. Nothing is auto-confirmed.
• Token and network are recorded on the payment, so USDC on Ethereum and USDC on Base are kept apart.

Invoicing

The Verbial Slack app sends each person their notifications as a direct message and posts team celebrations to a channel.

• Any notification, budget alerts, proposal signed, invoice paid, time reminders, can be delivered by Slack DM as well as in-app and email. Each person chooses per event and sets working hours.
• People are matched to Slack by email; no one has to link an account by hand.
• Optional culture posts: birthdays and work anniversaries in a channel, a weekly icebreaker, and /shoutout, /birthday and /hiredate slash commands.
• Slack does not receive deal, invoice or time data beyond the notification text and a link back.

Setup guide

Documenso is the e-signature backend behind proposals, agreements and estimates; clients sign on your branded page and never see it.

• The agreement PDF is generated from the proposal, the agency counter-signature is applied automatically, and the client signs from the proposal page on your domain.
• Completion is recorded from the signing page, the webhook and a reconciliation job, so a closed tab cannot lose a signature.
• The signed PDF is stored on the proposal and emailed to the agency.
• There is nothing to set up. Verbial runs Documenso for every workspace.

Proposals

Domain Rating and estimated organic traffic are fetched from Ahrefs for the domains in client reports.

• Domain Rating and monthly organic traffic estimates per domain, refreshed on a schedule and on demand from the report.
• Used on coverage and SEO report sections so metrics are fetched, not typed.
• Verbial supplies the Ahrefs access; no key or subscription needed from you.

Client reporting

View, like and comment counts for YouTube videos in client reports are fetched from the YouTube Data API.

• Paste a video URL into a coverage or report section and the counts fill in and refresh.
• Supports watch, shorts, embed and youtu.be links.
• Video titles are fetched for report items automatically.

Client reporting

Paid invoices reach QuickBooks Online through an accounting bridge: Verbial mirrors each paid invoice to an Airtable table that your Zapier automation posts to QuickBooks.

• Every invoice that moves to paid is written to an Airtable incoming payments table with the invoice number, client, brand, amount, payment method and a link back to the invoice.
• The row is keyed on the invoice number, so re-syncs update one row instead of duplicating it, and the "in QBO" columns are never overwritten once your automation sets them.
• Usage statements are excluded; they are retainer depletion, not a collection.
• Sync failures notify admins rather than failing silently.

Invoicing · Setup guide

The migration hub imports companies, contacts, deals and notes from HubSpot with a private app token or HubSpot's own CSV exports.

• Connect with a private app token or upload the CSV exports; field labels are recognised from HubSpot's export format.
• Companies match by domain, contacts by email, and every record keeps its HubSpot id so re-running is safe.
• Opt-outs carry over. An import can raise an opt-out, never clear one.
• Dry run first, then import, with a one-click rollback of the whole import.

CRM · Setup guide

Import organizations, persons, deals and notes from Pipedrive through its API or CSV exports.

• Paste an API token or upload the exports.
• Stages map to your pipeline by name; unmatched deals land on the first open stage and are listed.
• Owners match by email. Dry run and rollback included.

CRM

Import Accounts, Contacts, Opportunities and Notes from Salesforce reports or Data Export files.

• File import only. Export from a report or Data Export and upload.
• Salesforce field labels are recognised, Opportunity stages map to your pipeline, and record ids are kept for de-duplication.
• Dry run and rollback included.

CRM

Import leads as companies, contacts and opportunities from Close CSV exports.

• Upload Close's exports; matching is by email and domain.
• Dry run and rollback included.

CRM

Import Accounts, Contacts and Deals from Zoho CRM exports.

• Upload the exports; Zoho's labels are mapped and record ids are kept for de-duplication.
• Dry run and rollback included.

CRM

The migration hub imports clients, projects, tasks and every time entry from Harvest with your account id and token, or from CSV exports.

• Entries keep their dates, durations, notes and billable flags; people match your team by email.
• Project budgets and rates come across where Harvest had them.
• Dry run shows counts per entity before anything is written; the whole import can be rolled back.
• This is a one-time move, not an ongoing sync.

Time tracking · Setup guide

Import clients, projects and time entries from Toggl Track through its API or the detailed CSV report.

• Durations are kept to the second; start date and time are joined correctly from the CSV.
• Tags and billable flags come across; people match by email.

Time tracking

Import clients, projects, tasks and time entries from Clockify through its API or the detailed CSV export.

• ISO 8601 durations are parsed from the API.
• People match by email; dry run and rollback included.

Time tracking

Import clients, projects, tasks and time entries from Everhour with an API key or its exports.

• People match by email; dry run and rollback included.

Time tracking

Import companies as clients, projects, services as tasks and time entries from Productive.io export files.

• File import from Productive.io's exports.
• Budgets and time history come across so utilization is intact from day one.

Time tracking

Bring projects from Asana exports into Verbial as the clients and projects your team tracks time against.

• Export projects from Asana and upload; sections or custom fields can map to clients.

Time tracking

Bring boards from monday.com exports into Verbial as projects, with a client column mapped to clients.

• Export a board and upload; columns map to clients and projects.

Time tracking

Connect Claude Desktop, Claude Code or claude.ai to Verbial through its MCP server, with each person's own token and permissions.

• Each person creates a personal token; Claude sees exactly what that person can see, no more.
• Tools cover clients, projects, proposals, invoices, service items, time entries and summaries, and the CRM: companies, contacts, deals, lists, email, campaigns and workflows.
• OAuth is supported for clients that use it.
• Included on Growth and above, or as the API and Claude access add-on.

Setup guide

External services submit leads to Verbial with a scoped service token, and the lead lands exactly as a native form submission does.

• POST /api/v1/leads runs the lead through a real form: same dedup, company matching, validation, workflow triggers and owner notification.
• Tokens are scoped (leads:write) and bound to one brand; the brand comes from the token, never the request body.
• Idempotency keys prevent duplicate submissions on retries. Unknown payload keys are rejected.
• Included on the Scale plan, or as the API and Claude access add-on.

CRM · Setup guide

A rep connects Fireflies so proposal drafting can pull the calls they have already had with a prospect.

• Connected per person over OAuth; searches run as that person, so they see only the meetings they can see in Fireflies.
• Meeting context feeds the AI drafting panels on the proposal page.

Proposals