Marketo Integration - Incorrect "Connect" URL in Provider tab

[mscherr-fastspot]

Describe the bug

The Marketo Integration fails to properly connect following the official documentation here:

https://verbb.io/craft-plugins/formie/docs/integrations/crm#marketo

I removed the URL in the Redirect URI in the screenshot above for privacy

Plugging in the requested fields, the "Connect" link creates the following incorrect skeleton:

[FORMIE_MARKETO_CLIENT_DOMAIN]/identity/oauth/authorize?state=[state]&scope=&response_type=code&approval_prompt=auto&redirect_uri=[SITE_URL]/formie/integrations/callback&client_id=[FORMIE_MARKETO_CLIENT_ID]

After speaking with Marketo support, they let me know this is the correct URL to get a bearer token from their API:

[FORMIE_MARKETO_CLIENT_DOMAIN]/identity/oauth/token?grant_type=client_credentials&client_id=[FORMIE_MARKETO_CLIENT_ID]&client_secret=[FORMIE_MARKETO_CLIENT_SECRET]

I am unsure if Marketo changed their API, or released a new version. I appreciate any help.

Steps to reproduce

1. Follow the steps outlined here for Marketo: https://verbb.io/craft-plugins/formie/docs/integrations/crm#marketo
2. Click the "Connect" button in the "Provider" tab
3. Observe the connection does not work

Form settings

• Multi-page form: N/A
• Submission Method: N/A
• Client-side Validation: N/A
• Custom Form Templates: N/A

Craft CMS version

5.8.23

Plugin version

3.1.10

Multi-site?

No

Additional context

No response

[engram-design]

Ah right, looks like Marketo uses 2-legged OAuth 2.0 (Client Credentials Grant type), rather than 3-legged authorization code flow. I'm not sure if that's a new thing!

Fixed for the next release. To get this early, run composer require verbb/formie:"dev-craft-5 as 3.1.10".

[mscherr-fastspot]

I updated to that version, but am getting this error now when I click on "Connect":

Unable to process callback for “marketo”: “Getting unknown property: verbb\formie\integrations\crm\Marketo::scopes” /var/www/html/[folder]/vendor/yiisoft/yii2/base/Component.php:159

Do I need to do anything else beyond upgrading the plugin version?

[engram-design]

Just pushed up another fix for that. To get this early, run composer require verbb/formie:"dev-craft-5 as 3.1.10".

[engram-design]

Updated in 3.1.11.

[mscherr-fastspot]

Hey, I'm sorry. I upgraded to 3.1.1 and I am getting this new error regarding an access_token not being passed:

If you need me to debug anything, I'm happy to help!

[mscherr-fastspot]

So it's weird. The URL that works in the browser is this:

[client_domain]/identity/oauth/token?grant_type=client_credentials&client_id=client_id]&client_secret=[client_secret]

... with client domain NOT having /rest at the end, so something like: https://[number]-[string]-[number]-mktorest.com/ (even though the URL I get from Marketo has /rest).

In the URL, I get this kind of response:

{
    "access_token":"[access_token]",
    "token_type":"bearer",
    "expires_in":3508,
    "scope":"[some-email@email.com]"
}

In my previous comment, my .env file had /rest at the end, but if I remove it, I get this error now:

... which seems very similar, but different to the original error?

I hope this helps.

[engram-design]

Thanks for this, and sorry for the ongoing issue. I don't suppose it'd be at all possible to gain those credentials, or temporary credentials for testing? Just checking up on my Marketo account and looks like they've shut me out, and will need to get in touch with them to get the account back online to properly test.

No stress if you're unable to do that, but just in case you are, getting in touch via support@verbb.io would be amazing to get this sorted.

Otherwise, in the meantime I'll wait for Marketo to get back to me so I can test this properly.

That's odd seeing that scope error, and the scope being your email, I'm not sure where that's being set!

I have made a small fix for the access_token issue, but I'm flying a bit blind without an account to test properly. To get this early, run composer require verbb/formie:"dev-craft-5 as 3.1.11".

[mscherr-fastspot]

@engram-design unfortunately I'm doing this on behalf of a client (I work for an agency) so I can't give out the credentials.

I tried the dev-craft-5 branch again (pulled this morning 2/11/26) and I got the same error unfortunately (same line and everything).

I'll be on standby if you need any kind of testing, please let me know. Thank you for all the work so far.

[engram-design]

Yep, totally understand - just thought I'd ask to speed things along! Looks like that solved the access_token issue at least, but yes - something is going on with scopes...