Zapier

The Lantfly app for Zapier triggers zaps on run, mention and alert events, and starts actors and tasks from a zap.

Coming soon

The Lantfly app is not listed in Zapier yet. Until it is, use Webhooks by Zapier with the REST hook API (see Without the app below).

Connect your account

1. In Zapier, add a Lantfly step and click Sign in.

2. Enter:

   Field	Value
   Lantfly URL	https://lantfly.com (/api/v3 is added for you)
   API token	A full-access token from Settings → API & integrations in Lantfly

3. Zapier tests the connection with GET /api/v3/hooks/events.

Triggers

Trigger	Fires on	Options
Run Succeeded	ACTOR.RUN.SUCCEEDED	Only actor ID, only task ID (empty: every actor or task)
Run Failed	ACTOR.RUN.FAILED, ACTOR.RUN.TIMED_OUT, ACTOR.RUN.ABORTED	Only actor ID, only task ID
New Mention	LISTENING.MENTION.CREATED	Project (required)
Alert Fired	LISTENING.ALERT.FIRED	Project (required)

The triggers are REST hooks: turning the zap on subscribes it (POST /api/v3/hooks), turning it off unsubscribes it. The sample step reads recent real events (GET /api/v3/hooks/samples). Each delivery's X-Lantfly-Signature is checked, and unsigned or tampered requests are dropped.

Trigger data is snake_case, as the API sends it: id, user_id, created_at, event_type, event_data (actor_id, task_id, run_id, or project_id, mention_id, alert_id, rule_id) and resource (the run with status, default_dataset_id, started_at, finished_at…, or the mention or alert).

Actions

Action	What it does	Fields
Run Actor	Starts a run of an actor (POST /api/v3/actors/{actor}/runs).	Actor (ID or username~name, for example lantfly~web-scraper), Input (JSON), Wait for finish (seconds), Memory (MB), Timeout (seconds)
Run Task	Starts a run of a saved task (POST /api/v3/tasks/{task}/runs).	Task ID, Input override (JSON), Wait for finish, Memory, Timeout

Search

Search	What it does	Fields
Find Run	Finds a run by its ID, with its status and storage IDs (GET /api/v3/runs/{run}).	Run ID, Wait for finish (seconds)

tip

Zapier stops an action after 30 seconds, so waiting is capped at 25 seconds. For longer runs, don't wait: start the run, then use a Run Succeeded trigger filtered on the actor to continue in another zap.

Example: new results to a spreadsheet row

1. Trigger: Lantfly → Run Succeeded, Only actor ID = your actor.
2. Action: Webhooks by Zapier → GET https://lantfly.com/api/v3/datasets/{{resource.default_dataset_id}}/items?format=json&clean=1 with header Authorization: Bearer <token>.
3. Action: your spreadsheet or CRM step, mapped from the items.

For spreadsheets, the built-in Google Sheets export needs no zap at all.

Without the app

1. Add Webhooks by Zapier → Catch Hook and copy its URL.

2. Subscribe it once:

   Subscribe a Zapier catch hook

   curl -X POST "https://lantfly.com/api/v3/hooks" \
     -H "Authorization: Bearer $LANTFLY_TOKEN" \
     -H "Content-Type: application/json" \
     -d '{"target_url": "https://hooks.zapier.com/hooks/catch/…", "event": "ACTOR.RUN.SUCCEEDED", "source": "zapier"}'

3. Start a run to send a sample, then build the rest of the zap.

4. To stop, delete the subscription: DELETE /api/v3/hooks/{id}.

To start runs without the app, use Webhooks by Zapier → POST to https://lantfly.com/api/v3/actors/<actor>/runs with the body {"input": {…}, "wait_for_finish": 25}.