You can configure a source or workflow to receive events from any number of other workflows or sources. For example, if you want a single workflow to run on 10 different RSS sources, you can configure the workflow to listen for events from those 10 sources.
The ID of the workflow or component emitting events. Events from this component trigger the receiving component / workflow.
emitter_id
also accepts glob patterns that allow you to subscribe to all workflows or components:
p_*
: Listen to events from all workflowsdc_*
: Listen to events from all event sourcesSee the component endpoints for information on how to retrieve the ID of existing components. You can retrieve the ID of your workflow in your workflow’s URL - it’s the string p_2gCPml
in https://pipedream.com/@dylan/example-rss-sql-workflow-p_2gCPml/edit
.
Only pass event_name
when you’re listening for events on a custom channel, with the name of the custom channel:
See the this.$emit
docs for more information on how to emit events on custom channels.
Pipedream also exposes channels for logs and errors:
$errors
: Any errors thrown by workflows or sources are emitted to this stream$logs
: Any logs produced by event sources are emitted to this streamThe ID of the component or workflow you’d like to receive events.
See the component endpoints for information on how to retrieve the ID of existing components. You can retrieve the ID of your workflow in your workflow’s URL - it’s the string p_2gCPml
in https://pipedream.com/@dylan/example-rss-sql-workflow-p_2gCPml/edit
.
You can configure workflow p_abc123
to listen to events from the source dc_def456
using the following command: