Yielde

Integrations

What we plug into out of the box, what we wire up on request, and what is on the roadmap. No fake checkmarks — if it says Live, your tenant can use it today.

Live
6
On request
11
Roadmap
5

How the three buckets differ

Live means it ships with every workspace on activation. No setup call, no per-tenant wire-up.

On request means we wire it up for your tenant during onboarding (or after) using n8n. n8n has 400+ native nodes — most of the tools you already pay for are an evening of work, not a procurement decision. Tell us what you need.

Roadmap means it is genuinely on the list, with a rough trigger. The first paying tenant with a hard requirement usually pulls the date forward.

Payments

  • Paystack

    Live

    Primary billing rail. Card tokenisation in the trial flow, subscriptions for monthly billing, split-group payouts for the web-dev agency.

  • Stripe

    On request

    For non-ZAR tenants or tenants already on Stripe. Not the default rail; we have to do the integration setup per tenant.

Compliance

  • Documenso

    Live

    POPIA DPA signing, embedded in the dashboard before workspace provisioning.

Voice

  • Retell

    Live

    Inbound voice receptionist. End-to-end latency ~700 ms with managed gpt-5-mini. Your tenant's number forwards to a Yielde-hosted Retell agent.

Email

  • Resend

    Live

    Transactional email — trial start, billing, lifecycle. Templates live in the repo and are reviewable per tenant.

Auth + data

  • Supabase

    Live

    Magic-link auth, Postgres for account and lifecycle records, row-level security on every customer-facing table.

AI providers

  • LiteLLM gateway

    Live

    Every model call (OpenAI gpt-5 family, Anthropic Claude) routes through our self-hosted gateway. Per-tenant virtual keys, cost attribution per workflow, the browser never sees an upstream API key.

Email + Calendar

  • Gmail / Google Workspace

    On request

    Wired through n8n. Inbound triage, send-on-behalf, calendar reads/writes for the booking flow.

  • Microsoft 365

    On request

    Outlook mail + Microsoft Graph calendar through n8n.

Messaging

  • WhatsApp Business

    On request

    Two-way inbound/outbound through the WhatsApp Business API. Same Lead Qualifier scoring path as the web form.

  • Telegram

    Roadmap

    For tenants whose audience is on Telegram rather than WhatsApp.

Internal

  • Slack

    On request

    Notifications to operator channels (`#yielde-ops`), one-way only by default. Two-way command surface available on request.

  • Microsoft Teams

    Roadmap

    Channel notifications + one-way command surface. Slack-style wire-up.

CRM

  • HubSpot

    On request

    Scored leads write straight into HubSpot deals + contacts. Pull-down of HubSpot lists for re-engagement campaigns.

  • Pipedrive

    On request

    Same flow as HubSpot — Pipedrive deals + activities populated from inbound qualifier scores.

  • Salesforce

    Roadmap

    Enterprise demand — first paying tenant on Salesforce will pull this forward.

  • Zoho CRM

    Roadmap

    Local SA market has meaningful Zoho usage. Same pattern as HubSpot.

Data

  • Google Sheets

    On request

    Read or write tabs as the system of record when a customer is not yet on a CRM. Common in week 1.

  • Airtable

    On request

    Bi-directional sync for clients running their pipeline in Airtable bases.

Knowledge

  • Notion

    On request

    Read knowledge-base pages to ground the chatbot or voice receptionist; write meeting notes back.

Scheduling

  • Calendly

    On request

    For tenants who already run Calendly; the Yielde booking surface is otherwise built-in.

Forms

  • Webflow

    Roadmap

    Native Webflow form submissions into the Lead Qualifier without the operator copying an embed snippet.

Need something not on this list?

Email support@yielde.dev with the tool, what you want it to do, and where it sits in your workflow. We will tell you within a day whether it is a one-evening n8n wire-up, a one-week build, or a real product decision.