Skip to content
Yareta Docs

Integrations Setup Guide

Step-by-step connection instructions for each third-party integration listed under /[slug]/organization-settings → Integrations. For what to do when an already-connected integration stops working, see the Troubleshooting Guide and Operations Runbook §3 instead — this document is about connecting for the first time.

A heads-up before you start: the on-screen status badge on some integration cards (Typeform, Airtable, HubSpot, Slack, Zoom) currently reads “Coming soon” even though several of them are fully working today — don’t take that badge as the final word on whether a “Connect” button will work. Try the button; if it opens a real authorization flow, it’s live.

OAuth-based integrations (Airtable, HubSpot, Typeform, Slack)

These four connect the same way:

  1. From the Integrations tab, find the connector’s card and click Connect. This opens the provider’s own authorization page in a new tab.
  2. Sign in to that provider (if you aren’t already) and approve the requested access.
  3. The tab closes automatically and your Yareta integrations page updates to show the connection as active — you don’t need to manually refresh or paste anything back in.

Slack’s flow additionally carries your organization context through the authorization round-trip automatically, so you don’t need to specify which Yareta organization the Slack connection belongs to — it’s inferred from where you started the flow.

Fireflies.ai (API key + webhook secret — two steps)

Fireflies is the one integration that isn’t OAuth-based, and it requires a step on Fireflies’ own site partway through:

  1. Click Setup on the Fireflies card. You’ll be asked for your Fireflies API Key — find this in your Fireflies account settings and paste it in.
  2. After your key is accepted, Yareta shows you a webhook URL to register on Fireflies’ side. Go to app.fireflies.ai/settings → Developer Settings → Webhook, and enter that URL there.
  3. Fireflies will generate a webhook secret for that URL — copy it and paste it back into the Yareta setup screen to complete the connection.

Once connected, your linked Fireflies account(s) appear in a list with an Active badge and a Disconnect button, so reversing the connection later is a single click (with a confirmation prompt).

Meeting Bot / Transcription (Google Meet, via Recall.ai)

Unlike the connectors above, this isn’t something you set up once for your whole organization — it’s registered per submission, when you want a meeting automatically transcribed:

  1. From the relevant submission, open the meeting-bot setup.
  2. Select the meeting platform — currently only Google Meet is supported.
  3. Paste the Google Meet link for the meeting you want transcribed, and submit.

Bae HQ CRM

If your organization has Bae HQ CRM available, it appears as a simple enable/disable toggle rather than a connect flow — there’s no OAuth step or API key to enter. Turning it on triggers a one-time backfill of your existing submissions from Bae HQ, then keeps data in sync going forward via webhooks and periodic polling. A “Last synced” timestamp (and any sync error) is shown on the same card once enabled, so that’s the first place to check if data seems out of date.

Zapier

Zapier isn’t configured from the Integrations tab at all — it uses its own API key mechanism under Organization Settings → Developers → Zapier. See the User Guide’s Webhooks & Developer Tools section for how that differs from an outbound webhook or a Developer API key.

Not yet available

Zoom, Calendly, Salesforce, and F6S are listed on the Integrations tab but have no working connect flow behind them yet — their cards are placeholders. If a teammate asks why clicking their card does nothing, that’s expected for now, not a bug on your end; there’s currently no ETA published for when these go live.

Related documents: User Guide · Troubleshooting Guide · Operations Runbook