Chainlink Automation: From Keepers to Smarter Smart Contracts
Chainlink Keepers to Automation: Evolution of Services
Smart contracts cannot wake themselves up. That limit created Chainlink Keepers in 2021, and the service has changed its name, design, and home since.
Teams running live upkeep need the current picture, because Chainlink Automation is no longer the end of the story.
Chainlink Keepers launched in 2021, grew into Chainlink-Automation with v2.1 features such as log triggers, and is now being replaced by CRE workflows.
Official documentation lists mid-2026 deprecation dates for Chainlink-Automation, so existing users need a migration plan.
What Were Chainlink Keepers?
Chainlink announced Keepers at SmartCon in August 2021. The service used off-chain computation run by node operators to tell contracts when to act.
Early uses included time-based settlement, limit orders, and liquidations. Aave and Synthetix were among the early adopters.
Readers who want the wider network context can start with this Chainlink architecture guide.
How Did Chainlink Keepers Become Chainlink Automation?
| Stage | What changed | Source |
| August 2021 | Keepers announced | CoinDesk (Reported) |
| Rename date | Not found | verified |
| Automation v2.1 | Forwarders, log triggers, and data streams support | Docs |
| November 2025 | CRE announced live on mainnet | Chainlink blog |
| Q2 2026 | Automation and functions upgraded to CRE workflows | Chainlink review |
The rename date was not found in the pages read, so it stays unverified. The v2.1 guide simply stops mentioning Keepers.
What Did Chainlink Automation v2.1 Change?
The v2.1 migration guide describes a consensus-driven design with four gains:
-
Off-chain compute of 10 million gas, though the exact scope of that figure should be checked in the guide
-
Better reliability and performance
-
Log trigger support
-
StreamsLookup for retrieving Data Streams
One change breaks old contracts. Each upkeep now calls through its own forwarder address, so msg.sender changes.
A contract that trusts only the old registry address stops working until it allows the forwarder. For Chainlink Automation developers, this is the first thing to test.
Why Is Chainlink Automation Moving to CRE?
Chainlink's Q2 2026 review says Functions and Chainlink Automation were upgraded from stand-alone services to CRE workflows, with the same capabilities plus extras. It gives no timeline.
The migration page is more specific:
-
v1.x deprecated as of 30 June 2026
-
v2.1 is deprecated as of 31 July 2026, with a testnet cutoff of 24 June 2026
-
CRE is described as a superset that supports every chain Chainlink Automation runs on
Service-level deprecation is documented. Whether a specific upkeep is still executed today is not verified.
That page was last updated on 25 May 2026 yet uses past tense for later dates, so confirm with Chainlink before relying on any date. For the longer view, see the future of Chainlink’s outlook.
Chainlink Automation vs CRE: Key Differences
The table maps Chainlink Automation concepts to their CRE equivalents.
| Chainlink Automation | CRE |
| Upkeep with checkUpkeep() and performUpkeep() | Workflow in TypeScript or Go, compiled to WebAssembly |
| Time-based upkeep | Cron trigger |
| Log-trigger upkeep | EVM Log trigger |
| Custom logic upkeep | Handler calling evmClient.callContract() |
| Direct call from forwarder | Signed report through KeystoneForwarder to a receiver contract |
Off-chain checks from Chainlink Automation keep moving into the workflow handler, outside of on-chain gas limits.
How to Migrate Existing Upkeeps
The official migration page lists five steps for Chainlink-Automation upkeep:
-
Scaffold a project from the automation-migration-ts template.
-
Deploy AutomationReceiver.sol with the right forwarder address.
-
Authorize target calls with setCallAllowed().
-
Simulate, then deploy the workflow.
-
Cancel the old upkeep and withdraw its LINK balance.
Before starting, list every upkeep with its version, chain, and trigger type. That tip is editorial practice, not from the docs. Teams handling LINK balances may also want the Chainlink Staking v0.2 explainer.
Security and Risk Checks
-
Verify chain, registry, receiver and permissions before cancelling anything.
-
Cancelling is not migrating, and a cancelled Chainlink-Automation upkeep with LINK inside needs a withdrawal.
-
A wrong receiver or forwarder setup can block execution.
-
Audit permission changes before mainnet, because Chainlink-Automation keeps track of contract permissions.
-
Official pages disagree on timing, so dates may be stale.
-
This article reflects reading, not hands-on deployment, and is not technical, financial, or legal advice.
Final Thoughts
Chainlink-Automation grew from a 2021 keeper network into a mature trigger service, then became one capability inside CRE.
The practical lesson for Chainlink-Automation users is simple: check the registry version, read the official migration page, and test on a testnet first.
Readers following the wider ecosystem can check Chainlink news and the Chainlink price prediction page, though neither changes the migration steps. Anyone still running Chainlink-Automation should treat this article as a map, not a manual.
Disclaimer: This article is general educational information about Chainlink-Automation and CRE. It is not technical, financial, legal, or tax advice. Smart contract changes carry real risk, including failed execution and unrecoverable LINK balances
