Deploy a Trigger
A 4-step recipe with Pipedream. We can help you get access.
Recipe · 4 steps
Deploy a Trigger
with Pipedream · Webhook & Event Subscription Management
List, inspect, deploy, and verify a Connect trigger for an external user.
- Search the registry for triggers belonging to the target app so the caller can confirm the chosen trigger key exists.
- Retrieve the selected trigger component to confirm its configurable props before deploying it.
- Deploy the trigger for the external user with the supplied configured props and optional webhook destination.
- List the external user's deployed triggers to confirm the freshly deployed source is present.
What you'll need to have ready
- projectId: The project ID, which starts with proj_.
- environment: The Connect environment (development or production).
- externalUserId: Your end user identifier for whom the trigger is deployed.
- app: The ID or name slug of the app to filter triggers by.
- componentId: The key of the trigger component to deploy.
- configuredProps: The configured props payload required by the trigger.
- webhookUrl: Optional webhook URL to receive the trigger's emitted events.
For your developer
Arazzo workflow pipedream:deploy-trigger, 4 operations: listTriggers → retrieveTrigger → deployTrigger → listDeployedTriggers. Specs on APIs.io.