Zapier App

Install

# Zapier → My Apps → connect "AnswerLine"
# Settings: API key, API base URL, engines

Example

# Actions:
#   Run Monitor, continues with the answer once it arrives
#   Create Task, queues work; the Zap resumes on the webhook

Connect with an API key and pick the engines to offer. Run Monitor queues the request as a task and continues the Zap with the answer; Create Task queues it with your own options and resumes when the webhook delivers the result.

Zapier limits how long an action may run, so prefer Create Task for AI engines whose answers take longer.

How the app works

Zapier stops a create or search action after 30 seconds, requests and scripting included (Zapier operating constraints, checked 2026-09-17). An AI engine can take up to five minutes to answer, so a Zap calling the synchronous endpoint would fail on slow answers while the API still completed, and charged for, the call.

Neither action in the app waits on an engine. Both submit POST /v1/async/task with the step’s callback URL as the task’s webhook, then return. Zapier shows the step as waiting, and resumes it when the API delivers the finished task to the callback URL. Zapier accepts a callback for up to 30 days (Zapier CLI core reference, checked 2026-09-17), far longer than any task runs: a task has 4 hours to start and five minutes to finish once started.

Every step is an async task and costs the engine’s price. If the app is not available in your Zapier account, use Webhooks by Zapier with the same REST calls.

Connect your account

Add a connection with three fields:

Zapier tests the connection with GET /v1/credits, which returns 401 for a wrong key. Every request carries the key as Authorization: Bearer <key>.

Actions and search

Run Monitor

Continues the Zap with the engine’s structured answer, the same body the synchronous endpoint returns: success and result with its fields (for example result.text and result.sources for ChatGPT, result.newsResults for Google News).

If the task fails, the step fails with the API’s error code and message, for example EXTERNAL_SERVICE_ERROR: … (task <id>). Failed tasks are not charged.

Create Task

The same fields plus Priority (1 to 10, higher runs first, default 1). It continues with the complete delivered task status whether the task completed or failed:

{
  "task": { "id": "…", "taskType": "CHATGPT", "status": "COMPLETED", "priority": 1 },
  "credits": { "creditsToCharge": 0.0006, "creditsCharged": 0.0006 },
  "response": { "success": true, "result": { "text": "…" } }
}

Use Create Task when later steps should branch on the outcome with a Filter or Paths step on task.status, or when you want to record credits.creditsCharged.

Find Task

A search that looks up GET /v1/async/task/{taskId}. It returns the task with its status and, once finished, response, or no result for an unknown ID. Use it to recover results from a step that stopped waiting, or in a separate Zap that checks tasks by ID.

Cost per step

Task prices, which is what every step pays:

Add-ons, the same on every tier: +$0.00071 per extra Google Search page and +$0.00071 for its AI Overview. ChatGPT’s include flags and extra Google News results pages are free. Higher tiers, reached by 30-day spend, cost less. See balance and pricing.

Replays, idempotency and charges

Each submission sends an Idempotency-Key header. The API answers a resend of the same request under the same key with the task it already recorded, charged once, instead of creating another.

• With a mapped Idempotency Key (recommended), the key is your value. Map something unique to the trigger item, such as a row ID or form submission ID, combined with the engine and, for scheduled Zaps, the date. A replay of the run returns the existing task.
• Without a mapped key, the key is a SHA-256 hash of the step’s callback URL. Zapier exposes no run identifier to an action, so the callback URL is the only value unique to that step of that run.

Two edge cases:

1. The API’s request fingerprint includes the webhook URL. A replay under the same key but with a different callback URL is refused with 409 RESOURCE_CONFLICT. The refusal is free, and the replayed step does not receive the first task’s result. If you have the first task’s ID, Find Task returns it.
2. A step whose Zap is turned off or edited while waiting is not resumed. The task still runs and is charged if it completes; only Find Task returns it.

Errors outside task execution fail the step with CODE: message (HTTP status, request id …). A 429 is raised as a throttling error carrying the Retry-After delay when the API sends one, so Zapier can retry later. Quote the request ID when contacting support; error codes are listed in authentication and errors.

Zap recipes

Weekly AI answer check into Google Sheets

1. Schedule by Zapier, every Monday at 07:00.
2. Formatter by Zapier: Date / Time formats the run date as YYYY-MM-DD for use in keys.
3. AnswerLine: Run Monitor with Engine CHATGPT, the prompt you track, Country US, Additional Fields {"include": {"markdown": true}}, and Idempotency Key crm-prompt-chatgpt- followed by the formatted date.
4. AnswerLine: Run Monitor again with Engine GEMINI and a key ending in -gemini- plus the date.
5. Google Sheets: Create Spreadsheet Row with the date, prompt, each engine’s result.text and the url values from result.sources.

The Zap costs $0.0012 a week ($0.0006 for ChatGPT, $0.0006 for Gemini). A Zap per prompt works for a handful of prompts. For dozens or hundreds, submit one batch of up to 500 tasks from a script with the TypeScript or Python interface and receive results by webhook.

Alert when your brand drops out of an answer

1. Schedule by Zapier, daily.
2. AnswerLine: Run Monitor, Engine GEMINI, Prompt “What are the best tools for [your category]?”, Country US.
3. Filter by Zapier: continue only if result.text does not contain your brand name.
4. Slack: Send channel message or Email by Zapier with the prompt and the first sources.

This costs $0.0006 per day per prompt. For a deeper version with thresholds and competitor lists, see Zapier AI answer alerts and measuring brand mentions in ChatGPT.

Google News monitoring to a CRM note

1. Schedule by Zapier, every morning.
2. AnswerLine: Create Task, Engine GOOGLE_NEWS, Query "Acme Corp" acquisition, Country US.
3. Filter by Zapier: task.status exactly matches COMPLETED.
4. Your CRM’s Create note action with the title and link of each entry in response.result.newsResults.

See news monitoring for query patterns.

Without the app: Webhooks by Zapier

Webhooks by Zapier can call the REST API directly. Webhooks by Zapier is available on paid Zapier plans, not the free plan (Zapier help, checked 2026-09-17). Because of the 30-second action limit, split the work into two Zaps.

Zap 1: submit. Trigger of your choice, then Webhooks by Zapier: Custom Request:

{
  "taskType": "CHATGPT",
  "payload": { "prompt": "What are the best tools for invoicing freelancers?", "country": "US" },
  "idempotencyKey": "<trigger item ID>",
  "webhook": { "url": "<Zap 2 Catch Hook URL>" }
}

Zap 2: receive. Webhooks by Zapier: Catch Hook trigger, whose URL you put in Zap 1’s webhook.url, then a Filter that continues only when the task status field equals COMPLETED, then your action steps.

Catch Hook does not verify the Webhook-Signature header, and anyone who learns the hook URL can post to it. For anything beyond internal notifications, add a Webhooks by Zapier: GET step to https://api.answerline.dev/v1/async/task/ followed by the delivered task ID, with your Authorization header, and use that authenticated response instead of the delivered body. To verify signatures directly, receive deliveries in your own endpoint as described in the webhooks guide.

Avoid pointing a Custom Request at /v1/monitor/<engine>: any answer slower than the action limit fails the step while the API completes and charges the call.

The integrations guide covers connection settings for Zapier, n8n and LangChain on one page.

Other integrations