I saw this other post where several people were having difficulties creating connections with the Make API.
I had the same need to create a connection to Google Maps. This is the Body that worked for me.
{
“accountName”:“Google Maps”,
“accountType”:“google-maps”,
“apiKey”:“{{GoogleMapsAPIKey}}”,
“scopes”:
}
The two issues I had were 1) not knowing the name of the “apiKey” key value, and 2) not having the api key value encased in quotes.
I quite mistakenly happened upon it by eliminating the key altogether. The API then responded with what it was missing. Might work for other APIs as well.
{
“accountName”:“Google Maps”,
“accountType”:“google-maps”,
“scopes”:
}
1 Like
Thanks so much for posting your solution @denisetaylor68 .
Yes, you can quite easily create new non-oauth connections via the API (oauth connections are harder due to some implicit behaviors of “oauth” in web applications). I’m glad this worked for you.
As an “insider tip” for future readers, you can use the following endpoint to figure out what connection parameters are expected for a particular service (in your case, Google Maps). Please note: this endpoint is not officially documented and/or supported by Make (read: “it could change”).
GET /v2/imt-forms/connections/create
This end point will get a list of field names / values expected for the desired app connection
Required scopes: imt-forms:read
Query Parameters
- teamId [integer]The unique ID of the team in which the connection will be created
- type [string] The unique name of the connection type that is associated with the application
Note: connection types are not necessarily the same as app names. The can be different (Slack is a good example of this). To identify a connection type, check out how a current module is configured, by looking at a blueprint.
Examples of connection types: google-restricted, jira
I will reply with other posts with the “trick” on how to deal with oauth connections. Cheers.
See my reply on this post for tips on creating oauth connections.
2 Likes