➤ Product: OfficeRnD Flex

➤ Who: Admins

➤ Where: In Zapier (the Zap editor, Zap History, and the Apps page)

➤ Availability: The Essentials plan does not include the Zapier integration. Start, Grow, and Scale plans include it.

In October 2026, the OfficeRnD app in Zapier moves to version 1.2.15; a Zap that worked before can fail with a sign-in error. A Zap step can also stop and ask you to select an organization. You can fix sign-in and organization errors in Zapier by reconnecting or adding a new setting in the Zap step.

Version 1.2.15 runs every OfficeRnD trigger, action, and search on OfficeRnD API v2. Version 1.2.11 is the previous version of the OfficeRnD app in Zapier. If the fix doesn't work, you can switch the Zap back to version 1.2.11 and keep your automation active.

Prerequisites

Before you start, ensure that you have these items:

Access to the Zapier account that owns the Zap. You change the Zap steps and the OfficeRnD connection in that Zapier account.
The email address and password of a Flex user who is an organization owner. Version 1.2.15 accepts only organization owner credentials for a new connection.
The name of the organization each Zap must use if the Flex user owns more than 1 organization.

What changed in version 1.2.15?

Some behavior in version 1.2.15 is new by design. Behavior that is new by design is not an error. Compare what you see in Zapier with this table before you look for an error message.

Change	What you see in version 1.2.15
Connection form	The connection form has only email and password fields. The Client ID and Client Secret option is removed. Connections that already use a Client ID and Client Secret continue to work.
Owner access	The email address and password must belong to an organization owner in Flex.
More than 1 organization	Each OfficeRnD step has an Organization drop-down menu. You select the organization for the step there. A Flex user with only 1 organization is automatically connected to that organization.
Recurring bookings	The New Booking trigger runs 1 time for each occurrence of a recurring booking. Before version 1.2.15, the trigger ran 1 time for each booking series. Because of this change, you can see more Zap runs.
New output fields	The New Booking trigger and the Find Booking search return the member email and the resource type. The New Contract trigger returns the contract type.
New events	You can use the new New Ticket trigger and the new Find Contract search.

OfficeRnD moves your Zaps from version 1.2.11 to version 1.2.15. Your Zaps, fields, and connections continue to work after the move. You don't need to reconnect or rebuild your Zaps. New Zaps and new connections use version 1.2.15 automatically. To move your Zaps to version 1.2.15 earlier, contact OfficeRnD support.

Some changes are not expected. For example, a field that had a value in version 1.2.11 is now empty. Another example is a Zap that worked in version 1.2.11 and now fails with an error not listed in this article. If you see an unexpected change, switch the Zap back to version 1.2.11 and contact OfficeRnD support.

Find the error message of a failed Zap run

If the behavior you see isn't in the table of expected changes, the error message tells you which fix to use. Zapier keeps each failed run's error message in Zap History.

In Zapier, open Zap History. You will see a list of every run of your Zaps.
Open the failed run.
Find the step that is marked in red. The error message is displayed in that step.
Copy the full error message, or take a screenshot of the step. Each fix in this article starts with the exact error text, so you can match the text to the fix.

To find the fix, search this article for the first words of the error message. Keep a copy or screenshot of the error message, because OfficeRnD support asks for it if you contact them.

Reconnect your OfficeRnD account in Zapier

Most sign-in errors in this article end with a reconnect. A reconnect saves new Flex credentials for the OfficeRnD connection in Zapier.

In Zapier, go to Apps.
Find OfficeRnD and open the connection.
Click Reconnect to update the current connection. To create a separate connection instead, click Add connection.
Sign in with the email address and password of an organization owner in Flex. Version 1.2.15 accepts only organization owner credentials.
If you clicked Add connection, open each Zap that used the old connection. Select the new connection in every OfficeRnD step, and then publish the Zap. Each Zap continues to use the old connection until you select the new connection and publish.
If Zapier paused the Zap, turn it back on. A paused Zap does not run.
To process failed runs, replay them from Zap History.

Do not send your password, Client Secret, or API tokens to OfficeRnD support. Support doesn't need your credentials because you enter them only in Zapier.

Fix sign-in errors

A sign-in error means Zapier cannot sign in to Flex with the saved credentials. Each sign-in error has a different cause, so match the exact error text to the fix.

Fix a wrong or changed password

Zapier shows 1 of these errors when the password saved in Zapier does not match the password in Flex:

The email address or password you provided is not valid. If you recently changed your password, please reconnect.
Authentication failed — if you recently changed your password, please reconnect the Zapier account.

For example, the passwords do not match after you change or reset your password in Flex. To fix the error, reconnect with your current Flex password. You don't need to contact OfficeRnD support for this error. Reconnect your OfficeRnD account in Zapier.

Fix a connection that does not use an organization owner

Zapier shows 1 of these errors when the connected Flex user is not an organization owner:

The connected account must be an organization owner (admin level 3+).
The connected account must be an organization owner (admin level 3+). Please reconnect with an owner-level email and password.

The same errors are displayed when the Flex user has lost organization owner access. First, check in Flex whether the connected user is an organization owner. If the user is not an organization owner, do 1 of these actions:

Ask an organization owner in Flex to grant the user organization owner access.
Reconnect with the email address and password of a different Flex user who is an organization owner.

If the user is an organization owner and the error continues after a reconnect, contact OfficeRnD support.

Replace a Client ID and Client Secret connection

Zapier shows 1 of these errors when an older connection uses a Client ID and Client Secret that no longer work:

The Application Client ID or Client Secret you provided are not valid.
Authentication failed — the Application Client ID or Client Secret is invalid.
Authentication failed — the Application does not belong to the selected organization.
The organization this application belongs to cannot be connected to Zapier.

The Client ID and Client Secret come from an application in Flex. The connection fails if someone deleted that application in Flex. The connection also fails if someone created a new Client Secret for the application. A third cause is an application that belongs to a different organization than the organization selected in the Zap step.

Version 1.2.15 does not accept a Client ID and Client Secret for a new connection. To fix the error, replace the old connection with an email and password connection:

In Zapier, go to Apps and open the OfficeRnD connection.
Click Add connection.
Sign in with the email address and password of an organization owner in Flex.
Open each Zap that used the old connection. Select the new connection in every OfficeRnD step, and then publish the Zap. Each Zap keeps using the old connection until you select the new connection and publish.

Fix a connection with no usable credentials

Zapier shows this error when the saved OfficeRnD connection is incomplete:

This connection has no usable credentials. Please reconnect your OfficeRnD account.

This error usually occurs on very old connections. To fix the error, reconnect with the email address and password of an organization owner in Flex. Reconnect your OfficeRnD account in Zapier.

Fix organization errors

A successful sign-in does not tell a Zap step which organization to use. In version 1.2.15, each OfficeRnD step must point to 1 organization that the connected Flex user can access.

Select an organization in each Zap step

Zapier shows this error when an OfficeRnD step has no organization selected:

Organization is required for API v2 requests. Please select an organization in the Zap step.

The connected Flex user is an owner of more than 1 organization. The step doesn't tell Zapier which organization to use. To fix the error, select an organization in every OfficeRnD step:

Open the Zap in the Zap editor.
In each OfficeRnD step, select an organization from the Organization drop-down menu. Each step reads and writes data only in the organization that you select.
Test each OfficeRnD step. The test shows whether the step gets data from the correct organization.
Publish the Zap. Zapier uses the new organization settings only after you publish.

You don't need to reconnect for this error.

Fix an organization that the connection cannot access

Zapier shows 1 of these errors when the Zap step or the connection points at an organization that the Flex user cannot access:

Organization "<slug>" is not accessible with these credentials.
Could not reach organization "<slug>" (<code>). Please reconnect.

In these errors, <slug> is the identifier of the organization that the step points to. For example, the error occurs when someone removed organization owner access from the connected Flex user. The error also occurs when the step has the wrong organization selected. To fix the error, do these steps:

Confirm which organization the Zap must use.
If the step has the wrong organization selected, select the correct organization from the Organization drop-down menu. Then publish the Zap so that Zapier uses the correct organization.
If the step already has the correct organization selected, reconnect with the email address and password of an owner of that organization. Reconnect your OfficeRnD account in Zapier.

If the error continues after you reconnect with a confirmed organization owner, contact OfficeRnD support.

Switch a Zap back to version 1.2.11

Some problems in version 1.2.15 have no fix that you can do in Zapier. Switching back to version 1.2.11 keeps the Zap active while OfficeRnD fixes the problem.

Use this workaround if the fix in this article doesn't work. Also use this workaround for unexpected changes. For example, a field that had a value is now empty, or a trigger stopped. Another example is duplicate Zap runs that the recurring booking change does not explain.

Important: Select only version 1.2.11 in the version selector. OfficeRnD supports only version 1.2.15 and version 1.2.11 for customer Zaps.

Do these steps for each Zap that has the problem:

Open the Zap in the Zap editor.
Click the first OfficeRnD step.
In the step's app version selector, change the version from 1.2.15 to 1.2.11.
Make sure the connection and all step fields still have values. Then click Test. The test shows whether the step works on version 1.2.11.
Do steps 2 to 4 again for every OfficeRnD step in the Zap. Each OfficeRnD step has its own version setting.
Publish the Zap. Zapier uses version 1.2.11 only after you publish.
To process failed runs, replay them from Zap History.

After you switch a Zap back, contact OfficeRnD support and tell them which Zaps you switched. OfficeRnD then fixes the problem, so that you can move the Zaps to version 1.2.15 again. If you have many Zaps to switch, OfficeRnD support can move all your Zaps back to version 1.2.11 at the same time.

Contact OfficeRnD support

Some errors come from the OfficeRnD platform. A reconnect does not fix these platform errors, because your setup did not cause them.

Report a platform error

These errors are platform errors:

Auth misconfigured: ... or v2 auth misconfigured: ...
Caller token exchange failed: identity server returned ...
Per-org token exchange failed ...
Provision request failed: ...
Provision response did not include ...
Token response did not include access_token.
Could not resolve organizations: the service returned ... with a 5xx code

If you see a platform error, do not reconnect. Contact OfficeRnD support immediately. If the error blocks your work, switch the Zap back to version 1.2.11 while OfficeRnD fixes the problem.

Send the information that support needs

Send all of these details in your first message, so that OfficeRnD support can start the investigation without more questions:

Your organization name in Flex.
The email address of the Zapier account that owns the Zap.
The link to the Zap, and the name of the OfficeRnD step that fails. For example, New Booking or Find Member.
The exact error message, or a screenshot of the failed run in Zap History.
The date and time of the failed run, with the time zone.
The connection type: email and password, or an older Client ID and Client Secret.
Whether the connected Flex user is an owner of 1 organization or of more than 1 organization.
What you already tried. For example, a reconnect.
Which Zaps you switched back to version 1.2.11, if any.
For any field that changed, include an example of the field value before and after the change.

Do not include your password, Client Secret, or API tokens in your message.

FAQs

Do I need to reconnect my Zaps after the update to version 1.2.15?

You don't need to reconnect after OfficeRnD moves your Zaps to version 1.2.15. Your Zaps, fields, and connections continue to work after the move. Reconnect only if Zapier shows a sign-in error.

Can I still connect with a Client ID and Client Secret?

You cannot create a new connection with a Client ID and Client Secret in version 1.2.15. Connections that already use a Client ID and Client Secret continue to work. A new connection must use an organization owner's email address and password in Flex.

Why does my New Booking Zap run more often than before?

In version 1.2.15, the New Booking trigger runs 1 time for each occurrence of a recurring booking. Before version 1.2.15, the New Booking trigger ran 1 time for each booking series. For example, a weekly recurring booking with 4 occurrences now starts 4 Zap runs.

Why does my Zap step ask me to select an organization?

Your Zap step asks for an organization because the connected Flex user is an owner of more than 1 organization. Select the organization from the Organization drop-down menu in each OfficeRnD step, and then publish the Zap.

Can I move all my Zaps back to version 1.2.11 at the same time?

OfficeRnD support can move all your Zaps back to version 1.2.11 at once. Contact OfficeRnD support if switching each Zap one by one is too much work.

Fix connection and version problems in the OfficeRnD Zapier app

In this article: