This topic was automatically generated from Slack. You can find the original thread here.
When using Pipedream Connect w/Managed Auth - How do we handle things like HTTP / Webhook with authType: undefined - Does this mean we don’t need to trigger an auth? It seems to fail at the moment.
When using Pipedream Connect with Managed Auth, the handling of authType: undefined for an HTTP / Webhook connection can be confusing. Here’s how it works and what you should do: — ### What does authType: undefined mean? - If a connection or endpoint has authType: undefined, it means no authentication is required for that endpoint. - For example, a public HTTP webhook that anyone can POST to would not require authentication. — ### Should you trigger an auth flow? - No. If authType is undefined, you should not trigger any authentication flow. - Your code should skip any logic that expects to fetch, refresh, or validate credentials. — ### Why might it fail? If you are seeing failures, it’s likely because: - Your code or the Connect SDK is expecting an auth object (like pd.inputs["$auth"]) even when there is none. - You might be referencing properties on pd.inputs["$auth"] without checking if it exists. — ### How should you handle it in code? Always check if $auth exists before using it. Here’s a pattern you can use in your handler: export default defineComponent({ async run({ steps, $ }) { // Only use auth if it exists const auth = this.$auth; if (auth) { // Use auth credentials as needed // e.g., auth.api_key, etc. } // Proceed with your logic (e.g., process webhook payload) return { success: true }; } }); Or, in Python: def handler(pd: "pipedream"): auth = pd.inputs.get("$auth") if auth: # Use auth as needed pass # Continue with main logic — ### Summary - authType: undefined means no authentication is required. - Do not trigger an auth flow. - Check for the presence of $auth before using it in your code. - If you see errors, make sure you’re not referencing properties on a missing $auth object. — If you’re still experiencing issues or see specific error messages, please share the error details, or visit Support - Pipedream for more help!
Could I please have some help with this? We’re struggling to get the HTTP integrated into our platform as an action. The authType is unknown and we’re missing some fields
The props are:
{
name: "Send POST Request",
description: "Send an HTTP POST request to any URL. Optionally configure query string parameters, headers and basic auth.",
componentType: "action",
version: "1.1.2",
key: "http-post-request",
annotations: {
readOnlyHint: false,
openWorldHint: true,
destructiveHint: false
},
configurableProps: [
{
name: "http",
type: "app",
app: "http"
},
{
name: "httpRequest",
type: "http_request",
label: "HTTP Request Configuration",
default: {
method: "POST"
}
},
{
name: "includeHeaders",
type: "boolean",
label: "Include Response Headers",
description: "Optionally export the full response headers",
optional: true
}
]
}
But I’m unable to see the same props here as we see actually in the pipedream editor:
Yea that action is a bit of a special snowflake in our builder UI — that http_request prop type gets a lot of special handling in the frontend, it’s not well supported in the Connect API right now. Can you tell me more about your use case?
Ah okay - Maybe we’ll have to hide these things off. We’re helping businesses automate business workflows and we were going to use this to call Internal APIs, rather than having to build out integrations for each one
