Why is there a difference in the configured props object key for Jira Actions in the demo app?

Help
1

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

Hello ,
I have query related to Jira Actions.
I was testing the Jira Actions on this demo app (https://pipedream-connect-demo.vercel.app/)
For jira action (jira-create-issue), configured props are:

   "app": {
      "authProvisionId": "apn_jEh1XZJ"
    }

For jira action (jira-get-issue), configured props are:

   "jira": {
      "authProvisionId": "apn_jEh1XZJ"
    }

Why there is difference in configured props object key (app/jira)?

2

Before Connect, the apps configured props name didn’t have an enforced structure

3

So you won’t be able to assume the app name

4

And will have to rely on the Get Component response’s configure_props

5

Okay thanks
So how can I keep it generic? Is there any function I need to call for configure_props?

6

The Get Component API: Pre-built tools for your app or agent — Pipedream

7

That’ll return the configurable props, including the app

8

Check out the getting started guide if you haven’t yet: Pre-built tools for your app or agent — Pipedream

9

Got it.
Thank you so much for the help :100: