Pipedream Enrichment — Call RichAPI from an HTTP or Code Step

Search the Pipedream app registry for RichAPI and you get nothing. There is no maintained component, no pre-built action, no OAuth app. We are not going to imply one exists so the page reads better.

What you do get is the thing Pipedream is actually good at: a generic HTTP action, a Node.js runtime in the middle of the workflow, and environment variables that are not stapled to a single step. That covers the whole API, and it takes about four minutes.

A waterfall lookup that finds nothing returns HTTP 200. Pipedream's HTTP action sees a 2xx and hands the workflow a body with "success": false and "billed": false in it. If your next step is a Google Sheets append, you have just written a blank email into a list you will later send to.

So the step after the request is a code step:

export default defineComponent({
 async run({ steps, $ }) {
 const r = steps.enrich.$return_value;
 if (!r?.success || !r?.data?.email) {
 $.flow.exit("no email found, nothing billed");
 }
 return { email: r.data.email, status: r.data.status };
 },
});

$.flow.exit() ends that event cleanly rather than throwing, so your error rate stays honest and your retries stay meaningful.

The same guard belongs after email_verifier, where the miss case is rarer but the interesting case is a catch_all result that is neither valid nor invalid. Route it, do not treat it as a pass. See catch-all email handling.

Log the execution_log from a waterfall endpoints response to a Pipedream Data Store on misses, and after a week you can tell a bad input format from a genuinely unfindable person. It shows who ran and what each returned.

We do not publish the source roster, because it changes. The log is the honest version: not a list on a marketing page, a per-call record of who ran on your request.

Is there a RichAPI component in the Pipedream registry? No. HTTP action or code step. If that changes, this page changes.

Can I use Pipedream's Connect / OAuth flow? Not with us. We authenticate with a static header key, so a workspace env var is the right home for it.

Will a miss retry forever? Not if you exit on success: false. A miss is a 200, so Pipedream's automatic retries never fire on it, which is correct, since retrying an exhausted waterfall spends nothing and finds nothing.

Can I run one key per client? Named keys with per-key usage attribution, yes. See per-client API keys for agencies.

Does Pipedream's concurrency break anything? The key is shared, so parallel workflows draw on the same credit balance. Nothing about the architecture cares which workflow called.