Deel + RunwayCal

Connect a Deel API token, inspect supported people, contracts, and payment records, then approve the team mappings that belong in RunwayCal. The workflow does not change Deel or infer unsupported employer fees and foreign-exchange costs.

What connects

The Deel connection is a user-triggered read and review workflow. Approved people can become or link to RunwayCal team members, and supported recurring payment records can become cash commitments.

People and contracts

Supported names, role, team, location, start date, contract status, and compensation fields form review suggestions.

Team mapping

Users decide whether to create a team member, link an existing one, or skip the suggestion.

Supported payments

Recurring payment records can create RunwayCal commitments during an approved import, with provider IDs retained for duplicate protection.

Token control

RunwayCal stores the API token encrypted. Disconnect removes the local token; users must revoke it in Deel to fully end provider access.

Without Deel connected vs with Deel connected

Without Deel connected

  • Export supported people and contract details
  • Re-enter selected team costs
  • Track where each recurring payment came from outside RunwayCal

With Deel connected

  • Read supported Deel people, contracts, and payments
  • Review team-member suggestions
  • Approve supported team and commitment records
  • Retain Deel provider IDs for duplicate protection

Who uses this connection

Distributed teams reviewing payroll context

Inspect supported team and compensation records before adding them to the plan.

Finance teams reconciling headcount records

Link an existing RunwayCal team member to the corresponding Deel person.

Operators reviewing recurring payments

Bring supported recurring payment records into commitments with duplicate protection.

Connection boundary

The Deel connection is read-only at the provider and writes only approved records to RunwayCal. It uses a pasted API token rather than OAuth, so provider-side revocation remains a separate user responsibility.

API token · review before import

Review supported people and payment records before they enter the plan.

Deel owns worker and contract operations. RunwayCal uses selected records to support team-cost and commitment planning after explicit review.

The connection reads people, contracts, and available payment records. Compensation cadence is normalized for the suggestion, but the user still controls whether a person becomes a new or linked RunwayCal team member.

During an approved import, supported recurring payment records can create commitments. The implementation does not prove a complete employer-cost, fee, tax, invoice, or foreign-exchange model, so those claims are intentionally excluded.

The provider does not expose a revocation call used by this integration. Disconnect clears RunwayCal's encrypted token and provider links; the user should also revoke the token in Deel.

Keep worker administration in Deel. Bring reviewed team and recurring-payment context into RunwayCal when it belongs in the operating plan.

Review Deel data in RunwayCal

Connect the supported account, inspect available data, and approve what enters RunwayCal.