Can ChatGPT Generate Pipedream Workflows, Insert them into Github, and Automate Solutions for Auth Issues?

1

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

Hey everyone, my apologies if this has been discussed before. I’m LOVING the new github integrations thing… but I’m hungry for more. I want ChatGPT to cook up pipedream workflows for me. Example:

“email Teddy every week and ask for his hours for that week.”
this should output:

schema: workflow/2022.04
name: Email Teddy
settings:
  error_notification: true
triggers:
- id: ti_LET6BJn
steps:
- namespace: send_email
  runtime: nodejs18.x
  uses: gmail-send-email@0.0.11
  props:
    gmail:
      authProvisionId: <redacted>
    to:
    - <redacted>
    subject: Weekly Update Hours
    body: Hey Teddy, could you send me your hours for this week?

And insert into Github, merge to production on pipedream. SO HOT.

This should be extremely easy now that we’re just specifying YAML. it should be simple to teach GPT-4 the parameters for various triggers / actions and just get it to generate yaml on the fly, insert to github, merge to production.

the only missing piece is auth. For auth I see two options:

  1. pre-configure accounts beforehand for any apps you think you’ll use with ChatGPT
  2. come up with some kind of flow where you get handed off to pipedream’s interface for auth
    #1 seems almost possible today. the only issue I’m coming up against right now is that I can’t seem to be able to query accounts with the rest API. If we could, we should theoretically be able to reference that here right:
gmail:
      authProvisionId: <redacted>

this would be literally superpower level. thoughts?

2

100%! This is on our backlog.

3

re: auth / configuring some params, #2 is likely the direction we’re headed

4

Awesome. That definitely makes the most sense. For the particularly eager of us is there a workaround that allows for referencing existing auth accounts from the API or is that is just impossible today?

5

As Marco noted in that thread below, the general model you’re looking for isn’t supported today. You still have to create workflows from the builder, and we manage all the state / serialization.

Once that’s solved, and you can programmatically create workflows directly from YAML like you describe, we plan to implement the AI layer on top of it.

6

in that future model, I would envision support for linking connected accounts directly by ID or another mechanism, so you can deploy the workflow e2e when the connected accounts already exist

7

so ideally

gmail:
  authProvisionId: <redacted>

would work in the manner you describe

8

beautiful. ok makes sense.

9

looking forward to it