Legacy Test Applets Retain Service Key Authentication After IFTTT Connect Migration

Authentication divergence after Platform-to-Connect migration

When a private service is migrated from the legacy IFTTT Platform to the IFTTT Connect framework, the authentication mechanism for test-mode executions changes from a long-lived service key to short-lived OAuth tokens issued through the Connect authorization flow. However, test applets created before the migration continue to invoke the legacy endpoint using the original service key, while new test applets created after migration use the Connect OAuth handshake. IFTTT does not document an automatic migration path for these in-flight test applets.

Constraints and uncertainty

The legacy Platform sunset is targeted for late 2025, after which the service-key endpoint will be deprecated. Service developers need to know whether existing test applets will continue functioning until that date, whether they can be programmatically migrated to the Connect OAuth flow, and what happens to test-mode rate limits and the test_mode: true flag during the transition. The IFTTT CLI ifttt test command does not replicate the Connect token exchange, so offline validation of OAuth-scoped permissions remains unavailable.

What is the expected lifetime of legacy test applets after a service migrates to Connect? Is there a supported method to migrate or recreate existing test applets under the new OAuth flow without manual user intervention? How should CI/CD pipelines that rely on the legacy service key adapt before the sunset date?