Is the Private Action Key Accessible as the 'ID' in the 'client.actions.run()' Call?

Help
1

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

is the private action key accessible as the id in the client.actions.run() call

2

The private action key is not directly referred to as the id in the client.actions.run() (or pd.runAction) call. When invoking a private action, you use the action’s unique identifier (the actionId or id) in the run call. For public actions, this is typically the string like “gitlab-list-commits”. For private actions you publish, the id is the unique identifier assigned to your action when you publish it (not the “key” you might use locally). To find the correct id for your private action: - After publishing your private action, it will appear under “My Actions” in the Pipedream UI. - The id you use in the run call is the published action’s unique identifier, not a local file name or key. Example: ```
const resp = await pd.runAction({ externalUserId: “abc-123”, actionId: “your-private-action-id”, // ← This is the published action’s id configuredProps: { // your props here } });

3

This is better: Using Custom Tools - Pipedream

4

thanks for the docs. is using the connect api with your own custom actions available on the connect plan?

5

Using custom actions in Connect is currently part of the Business plan