Load ScienceLogic SL1 PowerFlow data in Python using dltHub
Build a ScienceLogic SL1 PowerFlow-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
ScienceLogic Skylar Automation (formerly PowerFlow) is an integration platform that provides a REST API to manage applications, steps, and system resources. The REST API base URL is https://<your_hostname>/api/v1 and all requests require a PF-APIKEY header or query parameter containing a generated API key token.
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading ScienceLogic SL1 PowerFlow data in under 10 minutes.
What data can I load from ScienceLogic SL1 PowerFlow?
Here are some of the endpoints you can load from ScienceLogic SL1 PowerFlow:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| applications | /api/v1/applications | GET | Retrieve a list of all available applications | |
| apikeys | /api/v1/apikeys | GET | Retrieve all available API keys | |
| steps | /steps | GET | Retrieve a list of steps | |
| reports | /api/v1/reports | GET | Retrieve a list of paginated reports | |
| apikeys_details | /api/v1/apikeys/{apikey} | GET | Get details of a single API key |
How do I authenticate with the ScienceLogic SL1 PowerFlow API?
Authentication is performed using an API key provided in the PF-APIKEY HTTP header or as a query parameter.
1. Get your credentials
To obtain API credentials for ScienceLogic SL1 PowerFlow (now Skylar Automation), navigate to the API Keys page within the user interface. Click 'Create API Key', assign the appropriate user role, and save the generated API key. Note that the full key is only displayed once upon creation and must be copied immediately. API requests are authenticated by including this key in the header under the key name 'PF-APIKEY' or as a query parameter named 'PF-APIKEY'.
2. Add them to .dlt/secrets.toml
[sources.sciencelogic_sl1_powerflow_source] api_key = "your_api_key_here" # Include in your code header or query parameter as PF-APIKEY
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
uv run dlthub ai toolkit install rest-api-pipeline
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the ScienceLogic SL1 PowerFlow API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
uv run python sciencelogic_sl1_powerflow_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline sciencelogic_sl1_powerflow_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset sciencelogic_sl1_powerflow_data The duckdb destination used duckdb:/sciencelogic_sl1_powerflow.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
uv run dlthub show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads /api/v1/applications and /api/v1/apikeys from the ScienceLogic SL1 PowerFlow API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def sciencelogic_sl1_powerflow_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://<your_hostname>/api/v1", "auth": {"type": "api_key", "api_key": api_key, "name": "PF-APIKEY"}, }, "resources": [ {"name": "steps", "endpoint": {"path": "steps"}}, {"name": "apikeys", "endpoint": {"path": "api/v1/apikeys"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="sciencelogic_sl1_powerflow_pipeline", destination="duckdb", dataset_name="sciencelogic_sl1_powerflow_data", ) load_info = pipeline.run(sciencelogic_sl1_powerflow_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("sciencelogic_sl1_powerflow_pipeline").dataset() sessions_df = data.steps.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM sciencelogic_sl1_powerflow_data.steps LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("sciencelogic_sl1_powerflow_pipeline").dataset() data.steps.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load ScienceLogic SL1 PowerFlow data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for ScienceLogic SL1 PowerFlow?
Request dlt skills, commands, AGENT.md files, and AI-native context.