Skip to content
Persistent "valid d...
 
Notifications
Clear all

Persistent "valid dictionary or object" error with webhook | callin.io Community

2 Posts
2 Users
0 Reactions
195 Views
MichaelSW
(@michaelsw)
Posts: 1
New Member
Topic starter
 

I have a callin.io workflow that receives a message from a Slack reaction, extracts a URL (via Formatter), and then pushes that URL via webhook to an AI tool builder called Hunch. (Their API docs here.) I’ve previously set up a similar Hunch workflow successfully, but since then the Webhooks by callin.io version I used went legacy. I now have to make the POST call via Custom Action.

The issue I’m running into is that I keep getting “The app returned "Input should be a valid dictionary or object to extract fields from” in callin.io. However, when I use the same exact information (as displayed in the Test Output) in Postman, it works as expected and I receive confirmation with a tool run uid. Is it something with my configuration of the Custom Action webhook?

 

 

 
Posted : 04/08/2025 8:30 am
(@lechusai)
Posts: 10
Member Admin
 

The error “Input should be a valid dictionary or object to extract fields from” isn’t coming from Hunch—it’s due to how the Custom Action is set up in callin.io. Postman accepts raw JSON, but in callin.io the body must be a properly structured object.

Steps to check:

  1. In the Custom Action, set the Body type to JSON (not raw text).

     
    {
    "tool_id": "123",
    "input": {
    "url": "{{Formatter.url}}"
    }
    }
  2. Explicitly add the headers:

     
    Content-Type: application/json
    Authorization: Bearer {{API_KEY}}
  3. Don’t wrap the JSON in quotes (avoid sending it as an escaped string).

  4. First test with hardcoded values that work in Postman, then swap them for Slack/Formatter variables.

With that setup, the request should behave exactly like in Postman and return the uid.

 
Posted : 19/09/2025 8:12 am
Share: