Skip to content

Update introduction.md #4

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update introduction.md #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/introduction.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ This document should help you navigate and access Leap's new workflows. Feel fre

When building a workflow on Leap you can create different types of actions, actions are essentially integrations on top of services which allow you to call each service with full flexibility while still benefiting.

Currently Leap supports OpenAi, Astria, and Replicate.
Currently Leap supports OpenAI, Astria, and Replicate.

The schema for each of the services follows the following structure:

Expand Down Expand Up @@ -106,6 +106,6 @@ The interface is very similar to actions, but with the addition of the `url` and

## On Service Webhooks

Its important to note that if a service accepts a webhook in the aciton body (e.g. Replicate), Leap workflows makes use of this value. And will ignore your value override it regardless of what you pass in the `body`.
It's important to note that if a service accepts a webhook in the action body (e.g., Replicate), Leap workflows make use of this value and will ignore any value you pass in the `body`, overriding it regardless of what you specify.

This is because webhooks need for the Leap engine to be aware of job completions. If you'd like to retrieve results, simply provide your `webhook url` when calling the Leap SDK or API, and not as part of step configurations.
This is because webhooks require the Leap engine to be aware of job completions. If you'd like to retrieve results, simply provide your `webhook url` when calling the Leap SDK or API, rather than as part of step configurations.