Getresponse Oauth2 problem

sjgn · February 17, 2021, 9:59am

hi there,
I’m new to n8n, and got stuck at the very begining. I can’t configure oauth2 connection to getresponse.

In the video / manual there are much less fields that I have in my instance of n8n:

And I cannot connect. Any help will be appreciated.

jan · February 17, 2021, 11:16am

Welcome to the community @sjgn!

You are showing two totally different credential types. The above one is of type “GetResponse OAuth2” and the one bellow from the generic type “OAuth2”.

The first one you should get displayed if you create credentials from the GetResponse-Node, the one bellow if you use the HTTP Request-Node.

sjgn · February 17, 2021, 12:47pm

Hello
@jan: I know. But I need to connect with Getresponse with HTTP Request node because Getresponse node only offers contact operations. I’d like to pull somehow reports.

And edit: for testing purposes - I can’t get the GetResponse OAuth2 to work either: it says ‘updated’, but does not redirect to getresponse to authorize (I’m using a ngrok tunnel on localhost).

jan · February 17, 2021, 1:20pm

You can then check the source code of the “GetResponse OAuth2” credentials. There you can find the values it uses:

github.com/n8n-io/n8n

packages/nodes-base/credentials/GetResponseOAuth2Api.credentials.ts

master

import type { ICredentialType, INodeProperties } from 'n8n-workflow';

export class GetResponseOAuth2Api implements ICredentialType {
	name = 'getResponseOAuth2Api';

	extends = ['oAuth2Api'];

	displayName = 'GetResponse OAuth2 API';

	documentationUrl = 'getresponse';

	properties: INodeProperties[] = [
		{
			displayName: 'Grant Type',
			name: 'grantType',
			type: 'hidden',
			default: 'authorizationCode',
		},
		{
			displayName: 'Authorization URL',

This file has been truncated. show original

Guess the problem is then that maybe something is not setup correctly. It is best and easiest to use the build-in n8n tunnel for testing purposes:

sjgn · February 17, 2021, 3:20pm

Thanks Jan. This helps a bit, I think I need to investigate further. The problem is probably in api endpoints and authorization urls, because I’m using a polish enterprise getresponse edition and it has everything setup differently…

jan · February 17, 2021, 3:40pm

Ah OK, that makes sense. Have no knowledge about that at all.

sjgn · February 17, 2021, 7:20pm

Jan,
I think I’ve found the issue. Figured out correct endpoints, but I need to pass additional parameter (X-domain with value) in header when authorizing. Is there a way to do it? I can add a header parameter in HTTP request, but cannot (or don’t know how to) do it when authorizing. Can you please help with this?

Edit: and it turns out, that when n8n gets an error respose when oauth2 authorizing - it crashes.

Topic		Replies	Views
oAuth2 : Password credential HTTP Request Questions credentials , node , http-request	6	1310	February 29, 2024
How to get access_token or another parameters from connected Oauth2 credential Questions credentials	3	1202	May 15, 2023
HTTP Requests Help me Build my Workflow	2	62	March 10, 2026
N8n API - Post /credentials with Oauth2 data schema Questions credentials , rest-api	8	3222	September 21, 2022
N8n OAuth2 (Client Credentials) credential not sending Bearer token in HTTP Reques Questions oauth2	9	192	April 22, 2026

Getresponse Oauth2 problem

Related topics