-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: add 3P workflow operations #31
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe remove this.
slug: get_temperature | ||
function: operation_handler | ||
type: action | ||
inputs: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we can add some comments explaining what these inputs are and how they are different from snap-in inputs.
14-operations/README.md
Outdated
|
||
The snap-in contains custom operations which can be used in the Workflow Builder once snap-in gets successfully activated. | ||
|
||
Operations are workflow node blueprint which are used to create workflow steps(nodes). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's remove node from here.
Co-authored-by: Kapil Garg <[email protected]>
Summary
Adding 3rd party workflow operations. These operations allow custom nodes in the workflow to be created by 3rd parties.
Work-item
https://app.devrev.ai/devrev/works/ISS-102170