Automation

Build AI-triggered workflows that send data to Sheets or webhooks.

Jobs

Jobs are automated “if this, then that” workflows. Choose what Querygen should watch, which conversations are in scope, and what should happen after a match. A job can create a task or lead, add structured data to Google Sheets or Supabase, or send a webhook.

A Job has three decisions

01
WatchPricing intent

Describe the customer signal in plain language.

02
ScopeAll direct messages

Choose exactly which conversations are eligible.

03
DoCreate a lead

Send the result to the tool where work continues.

The saved job

Create a lead from pricing enquiries

Adds qualified enquiries to the Sales board

New MessagesLead

All DMs · Not run yet

Shown with sample data. Controls are disabled in this guide.

Trigger Modes

Every job starts with a trigger. Choose the mode that matches the kind of activity you want to watch. The trigger only considers new activity after the job is enabled.

01

AI-detected pattern

Default

Querygen reviews new messages and triggers when the situation you described is present.

Choose it when: Use for sentiment, topics, or patterns that can unfold across several messages.

Examples: Customer frustration · competitor mentioned · contact details shared

02

New messages in a conversation

Runs when new messages arrive in a matching conversation, without requiring an AI pattern to be detected.

Choose it when: Use when any new activity in a known conversation should start the job.

Examples: A VIP customer writes · a selected support chat receives a reply

03

Every message

Each incoming message is checked individually against the condition you describe.

Choose it when: Use for structured requests and messages that contain all the required information at once.

Examples: Order with quantities · business card details · invoice data

04

An event occurs

Starts when a selected event is recorded for a contact or conversation.

Choose it when: Optionally require that an event did or did not happen within a time window, and combine multiple event rules with AND or OR.

Examples: Purchase completed · demo requested · no reply after an event

Conversation Filters

FilterMonitorsOptional name filter
All conversationsEvery DM and group
All DMsDirect messages onlyText pattern on contact name
All groupsGroup chats onlyText pattern on group name
SpecificHand-picked from searchable list

Actions

Choose the destination that matches the work you want to create. Task and lead actions keep the result inside Querygen. Google Sheets and Supabase add structured records to an external data destination. Webhooks send a request to another service.

Inside Querygen

Task · Lead

Create work the team can own and continue from the Tasks or Sales pages.

Google Sheets

Append a row

Choose a spreadsheet and sheet. Column descriptions tell Querygen what to extract into each field.

Supabase

Insert a record

Choose an authorized project and table, then map the information to add as a new row.

Webhook

Send a JSON request

Choose a saved endpoint and optionally shape the request with extracted fields and a body template.

Lead and Task Tracker Templates

Use the Lead Tracker or Task Tracker template when you want conversations to create work automatically. The setup guides you through the conversations to monitor and the information to capture. Lead Tracker is suited to sales enquiries such as pricing, quotes, demos, bookings, and purchase intent; Task Tracker is suited to assignments and follow-ups, including messages marked with #Task.

A lead tracker can also capture a shared business card: choose the business-card option in its lead action, then review the newly created lead and its source attachment on the Leads board. For either tracker, you can tailor the capture rule, owner or reminder settings, and the fields that should appear on the card before enabling the job.

Execution Logs

Select a job to open its status page. The chronological log shows whether the condition matched, what action ran, and any error that needs attention.

Success

The condition matched and the action completed.

Skipped

The job ran, but the condition did not match.

Error

The action failed. Expand the entry for details; someone with the relevant Write permission can retry it.