This topic was automatically generated from Slack. You can find the original thread here.
Hi folks, I don’t see an ‘Use external authentication’ option, which as per Pipedream blog can be used to connect an account with my users credentials? I am just starting with Pipedream in a free tier. Is this feature only available on paid tiers?
It’s available in the Free plan, you should see it when choosing a Connected Account in the step builder:
Do you see the Use external authentication button in the bottom right?
Here’s the docs on external auth: https://pipedream.com/docs/connected-accounts/external-auth
I just realised I was trying to find it on triggers… but I see it only on actions
here is what I am trying to do - let’s say my trigger is GitHub New issue creation - but I want to extend this functionality to my users to connect their GitHub accounts, and be able to trigger using their repo issues. How could I go about it?
Since I want to extend this as embedded within my app, I am thinking of using ‘Instantiate via API’ functionality after I build the workflow
Hmm good question. Not sure what’s the current state about triggers. do you know?
Triggers aren’t supported yet, only actions. Triggers use a different architecture (Sources) that are a separate Lambda instance from the main workflow environment
Thanks . Any timeline when external auth on triggers would be supported? Most of the workflows I was thinking depend on user authenticated source triggers, so that’s when pipedream will be more useful to me.
So there’s a major initiative to release Pipedream Connect, which allows you to connect your own users’ accounts to your Pipedream workspace.
And part of that effort is supporting this type of use case, where you can use credentials dynamically on sources and workflows.
How are you trying to reference these accounts’ credentials now? Do these credentials live on a managed database?
I am still in MVP build stages - so was evaluating Pipedream. I do plan to get user credentials (as needed by source) from my App UI, store them in a secrets store (on GCP), and then based use those credentials to connect accounts in user specific workflows, which I want to spin up dynamically when the user initiates the integration. Is there any tentative ETA for the Pipedream Connect project? I am also ok if I am included in the beta phase. If pipedream works for me from the onset, then I can use it for as many sources as possible.
Sure, here’s a link to the description of Pipedream Connect: Pipedream Connect
On this page you’ll also find a waitlist to sign up for early access. Definitely sign up so you can get access to this as well as get the opportunity to meet with the Pipedream team to give you use case to help influence the direction of this.
Great. will sign up. In the meanwhile, is there any workaround using the current functionality for what I am trying to achieve?
You can develop and deploy your own custom sources that retrieve the user credentials from your GCP managed database, and then perform actions with APIs on behalf of them.
All of the trigger source code is open source, so you can just reuse the methods on each of these components.
I’m not sure which apps you’re trying to automate in sources, but the code for each trigger is grouped by app in our public Github Repository here:
yeah I was able to use the source triggers - however, I wanted to extend the ability to my users to authenticate with their accounts, for those source triggers.
Yes, you can still do that by extending the existing source triggers and replacing the managed auth with a call do your database instead to refer to either one particular connected account or many.
Ok, so you are suggesting that through code, I can still enable my users to have their own source triggers. Did I understand correctly?
