Getting a different outcome with HTTP Module than I am with META Graph API Explorer

How To
1

I’ve been banging my head against the wall with this one all week, and am hoping someone here might have some insights.

I have a Make.com scenario that talks to the Meta Business API. One particular call I’m making using the HTTP module returns an “Invalid Parameter” error with a message about my “video needing to be uploaded to Facebook before creating the ad”. (The video has already been uploaded, my guess is that this message is a red herring.)

The odd thing is that when I make the exact same call using the Graph API Explorer tool, the call works.

The input bundle on the Make call:

[
    {
        "ca": null,
        "qs": [
            {
                "name": "access_token",
                "value": "EAAPb7Oxxxxxxxxxxxxxx"
            },
            {
                "name": "object_id",
                "value": "259352823939095"
            },
            {
                "name": "instagram_user_id",
                "value": "17841466299907139"
            },
            {
                "name": "source_instagram_media_id",
                "value": "17850902307207060"
            },
            {
                "name": "call_to_action",
                "value": "{\n        \"type\": \"LEARN_MORE\",\n        \"value\": {\n            \"link\": \"https://stream.ryanlangdonmusic.com/sams\"\n        }}"
            }
        ],
        "url": "https://graph.facebook.com/v19.0/act_299426824568894/adcreatives",
        "gzip": true,
        "method": "post",
        "headers": [],
        "timeout": null,
        "useMtls": false,
        "authPass": null,
        "authUser": null,
        "bodyType": null,
        "serializeUrl": false,
        "shareCookies": false,
        "parseResponse": true,
        "followRedirect": true,
        "useQuerystring": false,
        "followAllRedirects": false,
        "rejectUnauthorized": true
    }
]

Here is the JSON used in the Graph API Explorer:

{
  "object_id": "259352823939095",
  "instagram_user_id": "17841466299907139",
  "source_instagram_media_id": "18008642384233311",
  "call_to_action": {
    "type": "LEARN_MORE",
    "value": {
      "link": "https://stream.ryanlangdonmusic.com/sams"
    }
  }
}

And here a grab of that same call in the Graph API Explorer, with the response:

Graph_API_Call
Graph_API_Call2014×1096 108 KB

I am using the same access token in both cases. Is there something about the way I am passing parameters in Make that could be causing this? Any help greatly appreciated!

2

Since you are using the same request payload, and the outputs aren’t the same, it is likely a bug in the Meta Business integration/module.

For technical issues or bugs like this, directly contacting support can often lead to a faster resolution. They have access to your specific account details, scenario and scenario logs, server-side logs, and internal tools and resources, which allows them to investigate more thoroughly than what you have access to. Additionally, sharing sensitive information about your situation might not be suitable for an open forum discussion.

You can open a new ticket here, or if you are unable to login for some reason, you can create another new free account to access the ticketing system (which is only available to logged-in users).

If you manage to get your issue resolved with support, we’d still love to hear about it! Sharing your solution on the forum can help others facing similar problems.

samliew – request private consultation

Join the unofficial Make Discord server to chat with other makers!

2 Likes
4

Thank you for the response @samliew, I filed a ticket as you suggested, and will report back here when I get a response.

2 Likes
5

I ended up solving this using a different sequence of API calls to Meta. In my experience, there are occasionally some odd quirks with their API in terms of what you see in Graph API Explorer vs. responses in your own app. I believe the issue is on Meta’s side, not Make’s.

2 Likes