eltPulse

Getting started

eltPulse uses Clerk for authentication. After you sign up, we provision a user row in our database and you land on the dashboard.

1. Create a pipeline

  1. Open Pipelines.
  2. Pick Browse catalog, AI Builder, or Manual create mode.
  3. Pick a name (snake_case), source, and destination (manual / AI) or use the catalog wizard.
  4. Use Guided mode for GitHub or REST, or JSON for advanced configuration.
  5. Optional: add post-load dbt, link a workspace dbt project, or open the canvas after save.
  6. Submit — we store the definition and generate pipeline.py or replication.yaml, config.yaml, and eltpulse_workspace.yaml.

2. Review generated files

From the pipeline table, open Code to copy artifacts. Save them under eltpulse/pipelines/<name>/ in your managed repository when Git sync is connected.

3. Credentials

We never store source passwords in the product UI beyond optional BYO GitHub OAuth tokens (when enabled). Set environment variables in the runner or repo where you execute pipelines — see the sidebar hints on the builder for common keys (e.g. GITHUB_TOKEN, destination DSNs).

Next