← Back to workspace · All guides
Choose either manual file upload or the native OAuth-connected panel. Both use your existing QR link and inserting existing artwork uses no extra QR code place. The native app is in private preview; it is not yet publicly listed in Canva. Regular users do not generate keys.
Have a saved QR design and a Canva account. Manual upload needs no integration setup. The OAuth path also needs access to the private FutureQR Canva app. A paid Canva subscription is not required by FutureQR; Canva may charge for its own premium assets.
Check current plans and signup offersNo OAuth connection or developer keys needed.
Open a Canva design through the private FutureQR app preview link. The OAuth path lets Canva request access to the codes you authorize in FutureQR; it does not require customers to copy tokens. If the native app is unavailable, use Option A.
Choose Connect FutureQR. For production, check that the consent page is on futureqr.app. Sign in on the FutureQR consent page, choose personal codes or an authorized Pro client workspace, and approve. Uncheck Also request website-code creation unless you need to create codes from Canva. Canva manages the OAuth token exchange; never paste a REST/MCP credential or client secret into the design.
Search by code name or short code; Pro owners can filter authorized clients and campaigns. Select the code, review its saved style, then choose Insert QR into design. Keep the clear border and scan the final Canva artwork with your phone. Creating a website QR, when separately authorized, uses one of the owner's QR code places; insertion of existing artwork does not.
Use Disconnect in the Canva panel or Canva in the FutureQR menu → Revoke Canva access. Already inserted images remain in Canva. Reconnect to authorize access again. Destination changes keep the same QR; appearance changes require a replacement image. This section is for FutureQR app maintainers. Regular users and agency clients do not need a Canva developer app, API key or client secret. The native app already connects to FutureQR as its authorization server. The table above is for staging only. Production uses a separate app: App-owner setup: OAuth, client secret and Canva configuration
The file contains the secret; do not commit it, put it in the app bundle, share it in screenshots or paste it into a design.mkdir -p .deploy
(umask 077; set -C; openssl rand -hex 32 > .deploy/canva-client-secret.NEW.txt)CANVA_CLIENT_SECRET secret on the futureqr-staging Cloudflare Worker. Configure CANVA_APP_ID=AAHOGDu3VSI and CANVA_REDIRECT_URI=https://www.canva.com/apps/oauth/authorized. The public App ID is not a secret; this shared secret is generated by the FutureQR operator, not retrieved from Canva.futureqr provider, and enter the staging settings below. Copy the secret privately from the local file into Client secret; use the same value as the backend.Field Staging value Provider futureqrClient ID AAHOGDu3VSIMethod Client secretCredential transfer mode Headers (default)Authorization server URL https://staging.futureqr.app/oauth/canva/authorizeToken exchange URL https://staging.futureqr.app/oauth/canva/tokenRedirect URL supplied by Canva https://www.canva.com/apps/oauth/authorizedRevocation exchange URL https://staging.futureqr.app/oauth/canva/revokePKCE Enabled (S256)Multi-account Offcanva:asset:private:write and canva:design:content:write. A missing asset-write permission prevents insertion even when login and preview work.npm run build --prefix integrations/canva. Upload integrations/canva/dist/app.js under Code upload → JavaScript bundle. For local development, run a bundle server at the configured Development URL, such as http://localhost:8080/, and allow Chrome local-network access if prompted. Uploading a bundle does not prove the current preview is using it: check the source in Canva Dev Toolkit. Do not assume clearing the URL switches modes; the portal rejected that change during our test.AAHOGMPNoE0, provider futureqr, and Cloudflare Worker patient-snow-b392. Its authorize, token and revoke URLs start with https://futureqr.app, not the staging hostname. Use the production-specific secret, CANVA_APP_ID=AAHOGMPNoE0, and the same Canva-supplied callback https://www.canva.com/apps/oauth/authorized. Never mix the two apps, secrets or bundles. Build production with FQ_CANVA_BACKEND=https://futureqr.app npm run build --prefix integrations/canva and upload that output to the production app. A green checkmark and Saved beneath app.js confirm the upload; there may be no separate Save button. Open Preview using the uploaded JavaScript bundle, then verify the app source in Dev Toolkit or its source-bundle banner. The Development URL may still show localhost during preview; do not use it for this test. Production connection, QR insertion and a successful scan were manually confirmed on November 4, 2026. This is a working private preview; public Canva listing still requires review and approval.
Your QR appears in the Canva design and a phone scan opens its saved destination. Reconnecting restores access, and inserting an existing QR does not use another QR code place.
If production shows Failed to fetch (staging.futureqr.app), the app is running a staging-targeted bundle: the maintainer must upload the production build and reopen its bundle preview. Native Canva connection is not configured yet means the selected FutureQR backend lacks its matching OAuth settings; the maintainer must configure and deploy them. If a local-development preview cannot load from localhost, its development server must be running and Chrome must allow local-network access. An uploaded-bundle preview does not require a local server. For missing_scopes, the app owner must enable both Canva write permissions. Intent mismatch warnings mean the portal enables intents the app does not implement. If login is cancelled, expired or revoked, reconnect. Canva verification may need a person. Manual upload remains available.