Release R26-8 #
Available from 18th August 2026
Highlights #
Accounts > OAuth Client Credentials – new “Data on Demand” Scope
The Account-level OAuth Client Credentials has a new Scope: “Data On Demand”. This allows setup at the Cyclr Account level for the use of Cyclr’s Data on Demand feature, which enables calls to be made directly to Methods of installed Connectors through the Cyclr API.
Console > Settings > Notifications – additional measurement options
The existing Notifications feature, that allows you to be alerted as your Task Usage increases, has been extended by some additional measurement options:
- Pro rata: be notified if your daily Task Usage indicates you may exceed your Monthly Task Allowance.
- Absolute: be notified when your Monthly Task Usage reaches a specific number of Tasks.
The new “Absolute” option means this feature can now be used by Cyclr Partners with Private Instances, as they don’t have a Monthly Task Allowance to measure against using the original “Percentage” option.
MCP Servers – new Sign-In Tokens for separate users
When using Cyclr’s MCP Servers, we’ve added a new feature where you can create multiple “Sign-in Tokens” from a set of Account-level OAuth Client Credentials, allowing you to provide separate tokens, perhaps for use by each member of your team when calling Cyclr MCP Servers. That then enables you to view which of your users has made a call, as well as revoke access to an individual if necessary.
MCP Servers – new Workflow Tools feature
When using Cyclr’s MCP Servers, as well as being able to add Tools to them that call individual Connector Methods, you can now call entire integrations as Tools using Workflow Tools. This provides deeper control and fuller features that your MCP Servers can take advantage of, rather than having an external Large Language Model (LLM) figuring out how to perform a process by calling multiple separate Connector Methods each time.
Improvements #
Builder – first Step can be a Decision Step
Previously, Cyclr would not allow a Decision Step to appear as the first Step in a Template or Cycle. Being able to start with a Decision Step can be useful as it enables options such as using Script on it that checks the current date/time, enabling you to confirm whether you wish your integration to continue running or stop.
Builder > Step Setup – catching Lookup error for unauthenticated Connectors
Better displaying of error message when attempting to view a Lookup within the Step Setup popup of when the related Connector hasn’t been authenticated.
Console – minor text changes
We’ve made a very small change to the labels in a Cyclr Console’s side navigation, to hopefully make it clearer that you won’t find installed Connectors within the “Connectors” item:
- “Connectors” → “Connector Library”
- “Utility Connector Library” → “Utility Connectors”
- “Application Connector Library” → “Application Connectors”
Console > Reporting – Connector Report performance
The Console’s Connector Report could occasionally fail to load and display an error. Changes have been made to improve how it retrieves its data which should avoid this.
Console > Reporting – Task Usage chart axes corrected
After updating the chart library recently, the charts shown on the Account Task and Cycle Task Reports wasn’t displaying the Account or Cycle names. This Release corrects that.
Console Users – signing in directs you to Console, not Account Selection page
When signing into Cyclr as a Console User, sometimes you would be directed to the Account Selection page, where selecting one would sign you in as an Account User.
That behaviour has been corrected so that now you’re either taken to the Console Selection page (if you have access to more than one Console) else directly into your single Console.
This doesn’t affect how Account Users sign in.
Cycle Execution > File handling – large files and compression
Corrected how Cyclr was handling large HTTP-compressed files, where the host system used either gzip or deflate to reduce its size during transmission.
Cycle Execution > Webhooks – corrected missing Script situation
If a Template was installed into an Account to create a new Cycle, and that Template began with a Webhook Step which included Step-level Script, when the original Cycle was upgraded to a new Template Release (creating a new Cycle Version), the Script for the Webhook Step would not be executed when running the new Cycle Version. This Release corrects that behaviour so the Script will now be executed in the new Cycle Version.
Cyclr API – Authorization HTTP Header no longer case-sensitive for “bearer”
When making calls to Cyclr API endpoints, the Authorization HTTP Header previously required “bearer” (in exactly that character case) to appear before the Cyclr Access Token value. It now accepts any capitalization, e.g. “bearer”, “Bearer”, “BEARER”, etc.
Quick Connector > HTTP Request Steps – OAuth 2.0 Authorization Code corrected
Previously, if setting up a Quick Connector’s “HTTP Request” Step to use OAuth 2.0 Authorization Code, Cyclr wasn’t able to complete the authentication processes, resulting in you seeing a 404 error page. That has now been resolved.
Scripting – updated Moment.js time zones
Updated the time zones list used by the Moment.js JavaScript library to the latest. If you’re using Moment.js in your own Scripts, this ensures you are working with the most recent time zone settings.