RequestBin.com New User Workflow
@tod
code:
data:privatelast updated:1 year agoarchived
@tod/
RequestBin.com New User Workflow

Overview

This is the new user workflow that is triggered by new registrations on RequestBin.com.

Summary

  • A user registers on RequestBin.com
  • A slack message is sent to our internal "new user" channel notifying us of the sign up
  • The user's email is sent to RocketReach for enrichment (ie, to find out more information about the user, such as their title, company and social media profile URLs)
  • If there is enrichment data, the key data is sent back to the Slack channel
  • Lastly, all data including enrichment is sent to the Pipedream SQL destination so it is stored and queryable

Quickstart

Usage Tips

  • All pipeline code on Pipedream is public and run on every event. All event data is private.
  • Send data to Airtable, S3, Snowflake or HTTP out using code actions.
  • Event data is accessible in the $event object — add, update, or delete properties of this object in code.
  • Use $end() to stop your workflow or $respond to return a response to the client.
  • Most of NPM’s 400,000 packages are available for use — just require() them.
  • Store API keys or secrets as environment variables and access via process.env.KEY_NAME.
  • await the execution of async code with Promises, using async / await.
  • You need to await the execution of async code with Promises, using async / awaitlearn more here