Ifttt Python API Docs | dltHub

Build a Ifttt-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

IFTTT Connect API allows developers to connect their services and products to the IFTTT ecosystem for managing connections and triggering events. The REST API base URL is https://connect.ifttt.com and uses IFTTT-Service-Key header or Bearer token authorization.

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 Ifttt data in under 10 minutes.


What data can I load from Ifttt?

Here are some of the endpoints you can load from Ifttt:

ResourceEndpointMethodData selectorDescription
service_status/ifttt/v1/statusGETReturns status of the IFTTT service.
user_info/ifttt/v1/user/infoGETReturns information about the authenticated user.
test_setup/ifttt/v1/test/setupPOSTSets up and returns test data for integration testing.
trigger_check/ifttt/v1/triggers/{stepSlug}POSTChecks a trigger for new events.
query_perform/ifttt/v1/queries/{stepSlug}POSTExecutes a query to retrieve data from a service.

How do I authenticate with the Ifttt API?

The API supports two main authentication methods: Service-Key (passed in the 'IFTTT-Service-Key' header) for backend-to-backend communication, and Bearer token authentication (passed in the 'Authorization' header) for user-authenticated requests.

1. Get your credentials

To obtain your credentials for the IFTTT Webhooks service, first ensure the Webhooks service is connected to your IFTTT account. Navigate to the Webhooks service page on the IFTTT website and click the 'Connect' button if it is not yet active. Once connected, scroll to the 'About Webhooks' section at the bottom of the page and click the 'Documentation' link. Your unique Webhooks key will be displayed prominently at the top of the resulting documentation page. If you need to refresh your credentials, you can navigate to the Webhooks settings page (typically https://ifttt.com/maker_webhooks/settings) and click 'Regenerate key'. Note that if you are developing a professional IFTTT service (as opposed to using personal Webhooks), you obtain your 'Service Key' from the 'Details' tab within the IFTTT Platform dashboard.

2. Add them to .dlt/secrets.toml

[sources.ifttt_source] ifttt_webhooks_key = "your_key_here"

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 Ifttt 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 ifttt_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline ifttt_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset ifttt_data The duckdb destination used duckdb:/ifttt.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 GET /v2/me and POST /v2/connections/{connection_id}/actions/{action_slug}/run (for Connect API) or standard Webhooks trigger URLs like https://maker.ifttt.com/trigger/{event}/with/key/{key}. from the Ifttt 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 ifttt_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://connect.ifttt.com", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "service_status", "endpoint": {"path": "ifttt/v1/status"}}, {"name": "user_info", "endpoint": {"path": "ifttt/v1/user/info"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="ifttt_pipeline", destination="duckdb", dataset_name="ifttt_data", ) load_info = pipeline.run(ifttt_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("ifttt_pipeline").dataset() sessions_df = data.user_info.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM ifttt_data.user_info LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("ifttt_pipeline").dataset() data.user_info.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 Ifttt data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample 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 Ifttt?

Request dlt skills, commands, AGENT.md files, and AI-native context.

Available Pipelines