What are triggers and actions?
In Pipedream, we call triggers and actions components, which are self-contained executable units of code. Your end users configure the inputs and these components produce a result that’s exported as output. These components are developed and maintained by Pipedream and our community and their source code is available in our public Github repo.Check out the SDK playground to see the SDK in action. You can also run it locally and explore the code.
Implementation
You have two options for implementing Connect components in your application:- Use the
pipedream
backend SDK with your own frontend - Use the
connect-react
frontend SDK with Pipedream’s pre-built frontend components
Backend SDK
Use the Pipedream server SDK to handle all Connect operations on your backend, then build your own frontend UI. This gives you full control over the user experience.Connect React SDK
Use Pipedream’s pre-built React components to abstract the complexity of building a frontend form interface.Getting started
The following guide walks through using the backend SDK or REST API to manually discover apps, list components, and configure them. If you’re using the Connect React SDK, theComponentFormContainer
handles these steps automatically.
Refer to the Connect API docs for the full API reference. Below is a quickstart with a few specific examples.You can skip steps 1 and 2 if you already know the component you want to use or if you’d prefer to pass a natural language prompt to Pipedream’s component search API.
1
Authenticate to the Pipedream API
Before sending requests to the API, make sure to authenticate using a Pipedream OAuth client:
All subsequent examples assume that you’ve either initialized the SDK client or have a valid access token.
2
Find the app you want to use
To find the right trigger or action to configure and run, first find the app. In this example, we’ll search for Here’s the response:
gitlab
.3
List the available components for the app
Once you have the app you want to use, now you can list the triggers and/or actions for that app. We’ll list the actions for Gitlab and we’ll pass the Here’s the response:
name_slug
gitlab
as the app
.4
Next steps
Now that you’ve found the components you want to use, you can proceed to configure and execute them:
- For actions: See the Actions guide to learn how to configure props, handle dynamic props, and invoke actions
- For triggers: See the Triggers guide to learn how to deploy event sources and native triggers
- Need help?: Check the Troubleshooting guide for common issues and solutions