Catchline docs
v1.0.0
Get help
● Catchline · Operate

Start with the System check.
Then read the submission log.

The answers Catchline gives to form tools and Meta, and fixes for the problems you are most likely to meet: leads that do not arrive, failed submissions, Lead Ads, forms that do not show or send, timers, sequences and conversions.

Every failure has a reasonReplay after a fix

01First steps

  1. System check (Setup > System check, administrators): fix every red row; each says what to change. A late cron explains most "nothing happens" problems with timers, sequences, conversions and webhooks.
  2. Submission log (Leads > Submissions): if a lead reached your CRM, it is here with its status and, for a failure, the reason.
  3. The tool's own delivery log (Typeform, Tally, Google Ads, the Meta app's webhook page and so on) shows the HTTP answer Catchline gave.

02What the webhook link answers

AnswerMeaningFix
200 {"ok": true, …}Stored (with "duplicate": true when it already had it)Look in the submission log for the status.
401The signature, secret header or Google key is missing or wrongSave the same secret in the tool and in Catchline. For Lead Ads: the App Secret of the app that sends the webhooks.
403The source is switched offSwitch it on.
404Unknown link (wrong or rotated secret, deleted source)Create a new link and paste it into the tool.
405Not a POSTSet the tool's method to POST.
413Larger than Largest submission (default 512 KB)Raise it in Settings > Protection, or send fewer fields.
422The body could not be read in the tool's formatCheck the request format (JSON or form fields) in the tool.
429More than Submissions per minute, per connection (default 60)Raise it for big imports from a tool; the tool may retry.
503The module is deactivatedActivate it in Setup > Modules.

03Leads do not arrive

  • Nothing in the log: the request did not reach the CRM or was refused before it was stored (see the answers above). Check the link (it was shown in full only once), that the CRM is on a public https address, and that a firewall, a security plugin, Cloudflare or your host's WAF does not block POST requests to /catchline/.
  • Status Captured: the source has no mapping yet. Save the mapping, then Save and replay.
  • Status Failed with "The lead has no name": map a form field to Name, E-mail or Company. "No ticket department": choose one in the source's Setup. "A ticket needs an e-mail address": map E-mail.
  • Status In review: the review queue waits for your decision (always for a phone-only match).
  • Status Spam: the honeypot field was filled or the e-mail domain is blocked.

04Lead Ads

  • Meta says the callback URL or verify token could not be validated: paste both again from the source (the URL in full; create a new link if you no longer have it) and check that the source is switched on and the CRM is on https.
  • Test leads arrive, real ones do not: the Page is not subscribed to your app (the wizard shows Meta's error under the saved credentials; fix it and press Subscribe again, see step 4), the app is not live, or its permissions are not approved.
  • "Meta did not subscribe the Page": Meta refused subscribed_apps. Usually the Page token lacks pages_manage_metadata, belongs to someone who is not an admin of the Page, or expired. Save a new long-lived Page token (saving subscribes again) or press Subscribe again.
  • Leads show as failed with a Meta error: the Page token expired or lacks leads_retrieval, or the person behind the token has no access to the Page's leads. Save a new long-lived token, press Test the connection, then Fetch leads for the missed period.
  • Every notification answers 401: the App Secret saved is not the one of the app that sends the webhooks.

05Built forms

  • The embed shows nothing: the form is not published, it is archived, or its source is switched off (the script then says "this form is not published"). Check the browser console. A Content Security Policy on your website must allow scripts and connections to your CRM's address.
  • The iframe is blank: your CRM sends a header that forbids framing. Use the script embed.
  • "This page was open for too long": the form's token is valid for 24 hours; reload the page.
  • Visitors cannot send a form with a captcha: both keys of that captcha provider must be saved in Settings > Forms and spam, and the site key must allow your website's domain at the provider.
  • Every upload is refused: the PHP fileinfo extension is missing, or the file type is not ticked in the field's settings, or the file is larger than its limit or than PHP's upload_max_filesize.
  • Real people are marked spam: lower Fastest human for that form, check the blocked domains, or raise the per-visitor limit if many people share one office IP address.
  • A popup does not show: check its pages, devices and trigger; exit intent never shows on phones; a visitor who sent the form or saw it within "show again after" does not see it; the embed script is cached for up to 5 minutes.

06Routing, timers and alerts

  • Leads wait without an owner: nobody in the rule takes new leads, everyone is away or at capacity, and the rule has no fallback. Check the Sales team page.
  • Timers are late or never stop: the timer stops on a status change, a note, a logged contact or activity, which Catchline sees on the cron. Check that the cron runs every few minutes.
  • No e-mail alerts: Perfex's e-mail settings are missing (System check: Outgoing e-mail). No Telegram alerts: the bot token is saved by an administrator, the person's chat id is entered, and the person has started a chat with the bot.

07Follow-up sequences

  • Nothing is sent: the sequence is switched on, has an e-mail step, the lead has an e-mail address and matches Who joins, the send window allows the current time, the hourly limits are not reached, the address is not unsubscribed, and Perfex can send e-mail.
  • Replies do not stop the sequence: add a reply mailbox and press Test; the System check shows mailbox errors.
  • Opens look too high: some mail apps and security scanners load images and follow links. Treat opens as a hint, or switch tracking off.

08Conversions

  • Meta events fail: the log shows Meta's answer. Check the pixel id and access token; events older than 7 days are refused by Meta.
  • Google's file is empty: only leads with a gclid that became customers in the last 90 days are listed, and with invoice values only once the customer has an invoice. Leads converted after the payload retention period have lost their gclid (see Conversions).

09CSV import

  • The upload is refused: only .csv and .txt files of up to 10 MB; PHP's upload_max_filesize and post_max_size must allow the file (System check: Upload size).
  • The import stops part-way on a large file: the request ran into PHP's time limit. Import the same file again (rows already imported are skipped) or split it.
  • Strange characters: save the file as CSV UTF-8.

10Where errors are written

Errors outside the screens (cron steps, public addresses) go to Perfex's CodeIgniter log (application/logs/, when logging is on) and to the PHP error log, prefixed [catchline]. Include those lines when you ask for support, without secrets.