Controlled connections

Bring the data you already use into RunwayCal.

Connect supported accounting, CRM, payroll, payment and notification tools, or use file-based workflows where a direct connection is not the right fit.

RunwayCal keeps the source visible so you can review where the numbers came from.

How data becomes decision context

A controlled path, not a black box.

A connection should make data easier to use, not harder to explain. RunwayCal keeps the source and review step visible.

  1. 01

    Connect

    Authorize only the provider and organization you intend to use.

  2. 02

    Inspect

    Load the supported records and keep the source context visible.

  3. 03

    Approve

    For import workflows, choose what becomes a RunwayCal deal, receipt, team member, or commitment.

  4. 04

    Use

    Let approved records inform the connected planning outputs they support.

Nine implemented providers

Choose the connection by the job it performs.

All supported integrations are available on Pro and above. Founding Access inherits Pro-level availability. Connection behavior still varies by provider.

Accounting

Keep accounting in the source system. Review supported customer and received-payment records before they enter planning.

CRM & revenue

Inspect supported commercial records and decide which opportunities belong in the operating model.

Payments & collections

Separate provider activity from approved receipts and held cash. Each payment connection has its own control boundary.

PayPal

Pro and above

Review supported successful transactions before creating receipts or deal-and-receipt pairs.

Direction
PayPal → review → RunwayCal
Destination
Deals and receipts

Dodo Payments

Pro and above

Review supported successful customer payments before creating RunwayCal records.

Direction
Dodo Payments → review → RunwayCal
Destination
Deals and receipts

Payroll & people

Bring supported workforce context into RunwayCal without treating the payroll provider as an automatic ledger.

Notifications

Send selected RunwayCal notifications outward. Slack does not import financial data.

Slack

Pro and above

Deliver configured alerts and digests to a channel through an incoming webhook.

Direction
RunwayCal → Slack
Destination
Selected Slack channel

Three ways to bring data in

Use the path that matches the source.

Connected source

Keep a supported source connected.

Use a provider-specific review, refresh, event, or notification workflow. The source system keeps its original job.

Browse connection guides

CSV import

Map structured rows in bulk.

Choose a supported CSV workflow, map columns, preview the result, and confirm the import.

Explore CSV Import

Document upload

Extract fields from a supported document.

Upload a supported file, review extracted values, and approve the records that should enter RunwayCal.

Explore Upload & AI Import

Choose the right path

Bring the source in. Keep the numbers explainable.

Use the connection or import path that fits the data you already have.