Make and Google: No access token specified or 403?

A connection name is not a functionality check

An original report describes a connection apparently created immediately without a visible Google consent sequence, followed by a missing-token error. It does not confirm a particular device, country or browser as the cause. Q1 Make documents the Google sign-in and permission flow, connection verification and reauthorisation. Drive also offers different connection types. Q2 Q3 Q4

Separate missing authentication from a valid connection that cannot access one particular file. Both can stop a scenario, but the appropriate corrections differ.

Investigate the connection under control

1. Locate the exact failure. Does it occur during Verify connection or only in a particular module? Preserve the code, message and timestamp without tokens or complete authentication headers.
2. Check the selected connection. Compare team, connection entry and intended Google account. A similarly named entry or another signed-in browser account may direct the test towards a different identity.
3. Trace authorisation. Use the supported sign-in or Reauthorize flow. Establish whether account selection, requested access and return to Make complete successfully. If a step disappears or fails, capture that observation using an approved browser profile rather than disabling all security settings.
4. Verify the connection. If verification itself still fails because no token exists, investigate connection creation or hand the evidence to support first. Additional spreadsheet sharing cannot replace a missing access token.
5. Read one known test file. After connection verification succeeds, use the exact spreadsheet or file ID of an appropriate test resource. If only that resource fails, inspect access for the identity actually connected and the required permissions.

Consider other scenarios using the connection

Before reauthorising or replacing a shared connection, check which scenarios depend on it. Start verification with a read-only operation. Then observe the intended processes specifically rather than replaying every failed write without reconciliation.

Record the confirmed Google identity, connection type and successful read result. This provides a useful boundary between an OAuth issue and a later problem with file selection or module configuration.

Frequently asked questions

Can a Google API key replace the missing token?

Not automatically. Authentication must match the Make module and the private resources involved. Do not replace OAuth with another key type on a guess.

Must I create another Google account?

The message does not establish that requirement. Connection type, failing stage, observed browser flow and an anonymised test-file reference are more useful for assistance than another account.

Help with this case

We can help isolate the affected process and prepare a controlled next step. Discuss case A0351 with KAN KAI WORKS.