Questions about webhook trigger and invocations

This topic was automatically generated from Slack. You can find the original thread here.

Nicholas Reilingh : Curious about the pricing page FAQ – under “What are invocations?”, it describes a workflow with 5 steps triggered by an HTTP request counting as one invocation. But wouldn’t this be two invocations, since the HTTP endpoint is considered a source?

Tod Sacerdoti : Nicholas - thanks for the question. There is a native HTTP trigger that is distinct from using an HTTP event source. The native HTTP trigger does not count as an invocation whereas the HTTP event source does.

Dylan Sather (Pipedream) : Yes, if you choose the HTTP API trigger from the trigger menu on the right, you won’t incur an extra invocation. This clearly isn’t obvious now, and we’re planning to simplify how HTTP triggers work in a new version of the workflow builder

Nicholas Reilingh : Aha, that’s clearer now. (Here’s to turning that RSS icon green :wink:)

Nicholas Reilingh : Would it also be correct to say that the $respond() pattern is only supported by the native HTTP trigger?

Dylan Sather (Pipedream) : lol you’re right, that does stand out :laughing:

Dylan Sather (Pipedream) : that’s correct re: $respond()

Nicholas Reilingh : Gotcha, thanks! Perhaps review this part of the docs, then?

Dylan Sather (Pipedream) : wow yes, that is out of date (we actually used to have a separate native trigger called Webhook). I’ll make sure we get on that, thanks for catching that

Nicholas Reilingh : Actually forget what I said about turning the RSS icon green – that item (even though it’s on the right side of the select trigger panel) is not a native trigger since it does create a source. I was thinking that the green would be an indicator for native triggers, and indeed it is

Nicholas Reilingh : but it’s still a bit confusing to have it mixed in with the other native triggers

Dylan Sather (Pipedream) : good feedback from Nicholas re: the trigger menu

Pravin Savkar : Thanks for the feedback !