The users of your workflow
Yes, they should provide that info
It’s not an unknown variable or hidden
can you show me how to accept a string prop named “business_id” that represents a trustpilot business in a Node.js code step?
The step should make an HTTP request to the TrustPilot API and use the “business_id” variable in the URL as a route parameter
When you set up the Trustpilot Account in pipedream, there’s a field for the business unit ID which the user needs to select.
Presumably Pipedream could enumerate a list of available business unit IDs, but the Trustpilot account owner should be able to get the business unit ID themselves
Yes that’s the other option. You can leverage the TP API to make a step that just allows the user to select which business ID they’d like to use in the workflow or a particular step
I’m not seeing a specific API endpoint for listing all business units associated with the current TP API key, but you might be able to use this one: Business Units API - Trustpilot API Documentation
Why can’t we just use the business unit ID variable that the user sets at the time they connect to the TP account?
That’s what is in trustpilot.business_unit_id
Ah ok, so there is a business ID set at the time of authentication. But that variable will not be valid
I recommend taking a look at making a new Node.js step with the Trustpilot scaffolding, then connecting an account and then under Inputs you can find the proper path to the business unit ID
It’s not available at that path you’re currently expecting it to
I literally picked it from the little picker UI thing
Oh you’ve already connected TP to the HTTP request builder
I forgot we had that feature. That might be the cause in the share workflow link missing that connection
It’s not to do with the share feature - I think I noted above that I’m seeing the same thing in the original workflow (not just the workflow that was created using the share link)
You know what, I think it’s working fine, it’s just the display in pipedream is weird
Looking at the same place in “code” view, it shows these chevrons around it
I assume that’s because it’s classed as a secret?
Yes that could very well be it
The usual path in other steps is <app name>.$auth.<variable_name, this HTTP request builder feature is just different
Ok so I’m guessing it’s all fine and it’s just a bug in Pipedream where it’s urlencoding the <<trustpilot.business_unit_id>> text for displayhing in the Pipedream UI when it shouldn’t be.
Makes it look like it’s broken, or not picked up on the fact it’s an expression