How Does the Branching Impact Our Billing?

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

how does the branching effect how we are charged?

You should visit Pipedream for the latest pricing, but I’ll do my best to answer. Branching in Pipedream workflows—such as using conditional logic to run different steps based on data—does not directly affect how you are charged. Pipedream charges are primarily based on “credits,” which are consumed as your workflow runs. Each step in your workflow (including branches, actions, and code steps) consumes credits when executed. If your workflow branches and only certain steps run depending on the conditions, you are only charged for the steps that actually execute during that run. Steps that are skipped due to branching logic do not consume credits. However, if both branches are executed (for example, in parallel or due to your logic), then all executed steps will consume credits. In summary: - You are charged based on the number of steps that actually run, not the total number of possible branches. - More complex branching can lead to more steps being executed, which may increase credit usage if more steps run as a result. For more details on credit usage and pricing, please see Pipedream.

See here: Plans and Pricing - Pipedream