Ctrlk
Go to WebsiteLoginGet a Demo
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Perk

Connect Perk (formerly TravelPerk) so agents can work with trips, expenses, invoices and events through Cakewalk's gateway. No credentials to create; the one prerequisite is a Perk plan that includes

Connect your company's Perk account to Cakewalk's MCP Gateway. Every agent tool call against Perk passes through the gateway and is evaluated against your Policies.

Perk registers connecting applications automatically through OAuth Dynamic Client Registration. Nobody creates an app, and no credentials change hands. The setup is short because the real prerequisites sit on the Perk side: the right plan and the right roles.

The Perk MCP server can take action, not only read. Booking trips, submitting expenses and approving requests all run through it. Review your Policies for this Connection before employees connect.

Requirements

  • A Perk plan that includes integrations. On the free Starter plan, Perk blocks the authorization at the consent screen with the message that the Starter pricing plan does not include integrations.

  • A Cakewalk Admin, to enable the Perk Connection.

  • Perk covers TravelPerk and Yokoy spend data through this one Connection.

Step 1: Check Your Perk Plan

Open any Perk integration setting or start the connect flow once. If Perk shows that your pricing plan does not include integrations, upgrade the plan before continuing. No other Perk-side configuration is needed.

Step 2: Enable the Connection in Cakewalk

  1. Open https://app.getcakewalk.io.

  2. Go to Connections, select Add org connection, then Browse catalog.

  3. Select Perk and confirm.

There are no credentials to enter. Perk registers Cakewalk automatically on the first connect.

Step 3: Employees Connect

From an agent platform connected to Cakewalk, the employee connects Perk, signs in with their own Perk account and approves access on Perk's consent screen. Each call then runs with that employee's own Perk permissions, and each call is still evaluated against your Policies.

What Employees Can Reach

Access mirrors each employee's Perk role and your company's active Perk plan:

  • Expense insights need the Expense product active on your plan.

  • Reporting is limited to users with reporting access, which Perk restricts to analysts and account admins.

  • Trip lists return up to 30 trips per request and reporting data is one day behind by design. Both are Perk-side limits.

Verifying It Works

The Perk Connection card flips to Active on All Connections. From an agent platform connected to Cakewalk, ask the agent to list your upcoming trips. If Perk returns results, the Connection is live.

Troubleshooting

  • The consent screen shows the authorize button disabled with a pricing plan message. Your Perk account is on the Starter plan. Integrations, including this Connection, need a plan that includes them.

  • Expense questions return nothing. The Expense product is not active on your company's Perk plan, or the employee has no expense access.

  • Reports generate but the download does not open. Perk delivers reports as a download link, and the download runs through your company network, not through Cakewalk. Per Perk's allowlist article, add storage.googleapis.com and *.amazonaws.com to your company's firewall allowlist for reporting with the Perk MCP.

  • Sign in succeeds but tokens stop working later. Reconnect once. Perk's server tells clients to discard stale tokens and re-register automatically.

Learn More

PreviousOutreach
NextPersonio

Last updated

Was this helpful?