Instant trigger: retrieving additional data

Nerd-Zone
1

The docs here say that you can retrieve additional data for each bundle within the Communication section of the trigger.

The additional request looks like it’s being made to the correct URL, but returns a 403 (forbidden), even though it uses the same connection as all the other modules, and without the additional call it works.

This seems like maybe an auth issue, I tried adding the auth headers to this request but is still failing. What could I be missing? Thanks!

Instant Trigger → Communication
Without headers:

[{
    "url": "/files/{{payload.data.id}}/download-url",
    "response": {
        "output": "{{body}}"
    }
}]

With headers:

[{
    "url": "/files/{{payload.data.id}}/download-url",
	"method": "GET",
	"headers": {
        "x-api-key": "{{connection.apiKey}}"
    },
    "log": {
        "sanitize": [
            "request.headers.x-api-key"
        ]
    },
    "response": {
        "output": "{{body}}"
    }
}]

The call is being made to correct endpoint:

Integration Dropbox, Testing Copilot Make 2023-05-15 at 4.50.14 PM
Integration Dropbox, Testing Copilot Make 2023-05-15 at 4.50.14 PM3166×602 146 KB

TLDR our webhook doesn’t provide the download URL of a file in the response, a second call to get the download URL must be made.

In Zapier, we can make the additional call behind the scenes in the Zapier repo to return the download URL from the trigger, is this possible in Make?

2

It should work just fine, I have done multiple integrations with it and have done similar integration before with such settings.

As from the screenshot, it seems like the API Key is not being forwarded, it should pickup those from the base settings. Maybe try adding a new connection and see if it works with a new connection. Sometime, while developing custom app, the connection doesn’t seem to be stable.

1 Like
3

Thanks @Runcorn ! Tried with a new connection but still no luck. It works when manually passing in the API key to the headers object on the additional call, so I think you’re correct, so now we’re just stuck on getting it to inherit the connection :confused: