Make

You can use Lantfly in Make scenarios today with Make's built-in HTTP and Webhooks modules. No app to install.

Get an API token first: Settings → API & integrations in the Console (see API tokens). Use a full-access token if the scenario subscribes to events.

Run an actor

Add HTTP → Make a request:

Setting	Value
URL	https://lantfly.com/api/v3/actors/lantfly~web-scraper/runs
Method	POST
Headers	Authorization: Bearer <your token>
Body type	Raw, content type JSON (application/json)
Request content	{"input": {"startUrls": [{"url": "https://example.com"}]}, "wait_for_finish": 60}
Parse response	Yes

The answer is { "data": <run> }. Map data.id, data.status and data.default_dataset_id to the next modules. wait_for_finish (0–60 seconds) returns once the run finished or the time is up; for longer runs, continue from a webhook trigger.

To run a saved task, use POST https://lantfly.com/api/v3/tasks/<taskId>/runs with the same body (the input replaces fields of the task's input).

Read the results

Add another HTTP → Make a request:

Setting	Value
URL	https://lantfly.com/api/v3/datasets/{{datasetId}}/items
Method	GET
Query string	format = json, clean = 1, limit = 100
Headers	Authorization: Bearer <your token>
Parse response	Yes

Then add Flow control → Iterator on data to handle one item at a time. Use offset to page through large datasets. See Datasets for all parameters.

Trigger a scenario on Lantfly events

1. Add Webhooks → Custom webhook as the first module, create a webhook and copy its URL.

2. Subscribe the URL once, from a one-off HTTP module or a terminal:

   Subscribe a Make webhook to new mentions

   curl -X POST "https://lantfly.com/api/v3/hooks" \
     -H "Authorization: Bearer $LANTFLY_TOKEN" \
     -H "Content-Type: application/json" \
     -d '{
       "target_url": "https://hook.eu1.make.com/…",
       "event": "LISTENING.MENTION.CREATED",
       "project_id": "<projectId>",
       "source": "make"
     }'

   For run events use "event": "ACTOR.RUN.SUCCEEDED" (or ACTOR.RUN.FAILED, ACTOR.RUN.TIMED_OUT, ACTOR.RUN.ABORTED, ACTOR.RUN.CREATED) and optionally actor_id or task_id instead of project_id.

3. Click Redetermine data structure in Make, then start a run (or wait for a mention) so Make learns the payload: event_type, event_data and resource.

4. Keep the answer's id. To stop, unsubscribe with DELETE https://lantfly.com/api/v3/hooks/<id>.

Verify deliveries

Every delivery carries X-Lantfly-Signature: sha256=…, an HMAC-SHA256 of the raw body with the secret from the subscribe answer. Make's custom webhook cannot check it by itself; if the scenario does something sensitive, add a filter on a value only you know, or route the webhook through your own server. See Webhook signatures.

Example: alert to email

1. Webhooks → Custom webhook, subscribed to LISTENING.ALERT.FIRED with your project.
2. Email → Send an email with resource.project in the subject and the alert fields in the body.

Example: daily crawl to a database

1. Schedule the scenario once a day (or use a Lantfly schedule and a webhook trigger).
2. HTTP: start the actor with wait_for_finish: 60.
3. HTTP: read the dataset items.
4. Iterator → your database module.