This topic was automatically generated from Slack. You can find the original thread here.
Hi, we are interested in using Pipedream Connect but mainly for the OAuth client. We will run the workflows, triggers/actions on our own platform but want to provide users (and our devs) a streamlined way to add support for lots of apps. How does pricing work in this scenario?
When you say you’ll run the workflows, triggers/actions on your own platform, does that mean you’re looking to execute actions and deploy triggers via API, and not run Pipedream workflows?
Just want to confirm
yes that is correct - want to run the actions and delay triggers via API we just need something to help us scale the auth side of things
Yea that’s a core part of Connect — have you checked out the managed auth quickstart or Connect docs in general?
• General Connect docs: GitHub
• Managed auth quickstart: GitHub
• Tools via API: GitHub
Yep we have, but we are still not sure about the pricing…does each request for the auth get charged even though we are executing the action?
We need to improve the documentation on that front — these are the billable events:
• Action executions
• Trigger invocations
◦ A trigger is invoked every time it polls for changes (that schedule is up to you the developer to define), or when it receives a webhook event
• Requests to the Connect proxy
can you clarify what is meant by “Requests to the Connect proxy” - is this done on every request? or just once when the user goes through the oauth flow?
The Connect proxy gives you the ability to send custom requests to any integrated app on behalf of your end users, so if you don’t want to use a prebuilt tool or we don’t have one that fits your need exactly, it can give you more flexibility.
Does that make sense?