Browse 116 runnable templates across a range of industries. Every listing maps to a catalog-specific code artifact in the Admin Library and describes the input, configuration, prerequisites, and result for that workflow.
Done-for-you template offers are $500 to $1,500. Custom builds are $500 to $10,000 one-time, and monthly maintenance is $99 to $2,000/month. You may choose templates, custom builds, or both; monthly maintenance is a separate service. Scope and pricing are confirmed before work.
Named template offers:Lead Intake AI checks home-service inquiries and returns a routed result with an AI summary; Agency Client Intake AI checks project inquiries and returns an assigned result with an AI summary; and Real Estate Intake AI checks buyer and seller inquiries and returns an assigned result with an AI summary.
Business owners: Review each listing's input and configuration requirements before running its automation.
Entrepreneurs: Contact the owner with a general inquiry about a template.
General business workflows · Runnable code template
Lead intake and follow-up
Compares the supplied document list with a configured checklist and reports present and missing items for lead intake and follow-up.
How Lead intake and follow-up works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Documents
3
Create the resultReports whether required documents are complete and lists any that are missing.
Inputs: JSON input with records containing: id, approved, documents. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. A configured requiredItems document checklist.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
General business workflows · Runnable code template
Customer information requests
Checks supplied records against configured business rules and prepares a customer information requests follow-up result.
How Customer information requests works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based follow-up draft for each eligible record.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
General business workflows · Runnable code template
Document and report workflows
Compares the supplied document list with a configured checklist and reports present and missing items for document and report workflows.
How Document and report workflows works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Documents
3
Create the resultReports whether required documents are complete and lists any that are missing.
Inputs: JSON input with records containing: id, approved, documents. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. A configured requiredItems document checklist.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
General business workflows · Runnable code template
Internal content preparation
Uses the Polsia AI proxy to prepare a internal content preparation draft from supplied approved facts; the named reviewer checks it before use.
How Internal content preparation works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Source facts
3
Create the resultCreates an AI draft using the supplied source facts.
Inputs: JSON input with records containing: id, approved, approvedFacts. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. POLSIA_API_KEY provisioned for the Polsia AI proxy in the deployed app.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. For AI output, the deployed app needs POLSIA_API_KEY provisioned for the Polsia AI proxy.
General business workflows · Runnable code template
Internal handoffs
Checks supplied internal handoffs records against configured rules and returns a priority and assigned-owner handoff.
How Internal handoffs works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultReturns priority, rule result, and assigned owner.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
General business workflows · Runnable code template
Scheduling coordination
Checks supplied scheduling coordination records and returns the first supplied available option when present; it does not book or change a schedule.
How Scheduling coordination works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Available times
3
Create the resultReturns the first supplied available time; it does not make a booking.
Inputs: JSON input with records containing: id, approved, availableSlots. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Checks supplied records against configured eligible season or due date rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Seasonal service follow-up works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied urgent service inquiry records against configured required fields and business rules, then returns a rule-based result and assigned reviewer.
How Urgent service inquiry works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultReturns a rule result and the assigned owner.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Checks supplied records against configured plan or account status rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Maintenance-plan follow-up works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied urgent repair request records against configured required fields and business rules, then returns a rule-based result and assigned reviewer.
How Urgent repair request works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultReturns a rule result and the assigned owner.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Checks supplied records against configured estimate or proposal status rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Estimate follow-up works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied records against configured completed-work status rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Post-service feedback works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied records against configured audience eligibility rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Recurring service follow-up works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied records against configured eligible season or due date rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Seasonal customer outreach works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied records against configured audience eligibility rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How New-customer outreach works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied project update workflow records against configured rules and returns a priority and assigned-owner handoff.
How Project update workflow works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultReturns priority, rule result, and assigned owner.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Checks supplied trade-partner coordination records against configured rules and returns a priority and assigned-owner handoff.
How Trade-partner coordination works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultReturns priority, rule result, and assigned owner.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Checks supplied records against configured estimate or proposal status rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Proposal follow-up works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied technician visit brief preparation records against configured rules and returns a priority and assigned-owner handoff.
How Technician Visit Brief Preparation works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultReturns priority, rule result, and assigned owner.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Checks supplied work-order closeout exception review records against configured rules and returns a priority and assigned-owner handoff.
How Work-Order Closeout Exception Review works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultReturns priority, rule result, and assigned owner.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Checks supplied records against configured eligible season or due date rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Pre-Summer AC Tune-Up Campaigns works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied records against configured eligible season or due date rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Pre-Winter Furnace Check Campaigns works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied records against configured audience eligibility rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Equipment Age Replacement Outreach works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied after-hours lead capture records against configured required fields and business rules, then returns a rule-based result and assigned reviewer.
How After-Hours Lead Capture works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultReturns a rule result and the assigned owner.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Checks supplied same-day dispatch automation records and returns the first supplied available option when present; it does not book or change a schedule.
How Same-Day Dispatch Automation works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Available times
3
Create the resultReturns the first supplied available time; it does not make a booking.
Inputs: JSON input with records containing: id, approved, availableSlots. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Checks supplied records against configured business rules and prepares a missed call recovery follow-up result.
How Missed Call Recovery works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based follow-up draft for each eligible record.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Checks supplied records against configured audience eligibility rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Post-Repair Upsell Sequences works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied records against configured plan or account status rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Renewal Reminders & Annual Check Scheduling works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied commercial contract management records against configured rules and returns a priority and assigned-owner handoff.
How Commercial Contract Management works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultReturns priority, rule result, and assigned owner.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Checks supplied records against configured completed-work status rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Post-Job Review Request Automation works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Creates a response draft from customer-approved positive or negative response text using the supplied rating; a person reviews it before use.
How Negative Feedback Interception works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Rating
Customer feedback
3
Create the resultCreates a response draft from the configured positive or negative text.
Inputs: JSON input with records containing: id, approved, rating, reviewText. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Customer-approved positive and negative response templates.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Checks supplied records against configured record status rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Referral Request Sequences works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied automated patient inquiry response records against configured required fields and business rules, then returns a rule-based result and assigned reviewer.
How Automated Patient Inquiry Response works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultReturns a rule result and the assigned owner.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Uses the Polsia AI proxy to answer a supplied question from configured approved knowledge entries; unanswered questions are marked for staff response.
How Patient FAQ Chatbot works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Question
3
Create the resultCreates an AI answer from the configured knowledge base, or flags unanswered questions.
Inputs: JSON input with records containing: id, approved, question. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. An approved knowledgeBase with answer entries. POLSIA_API_KEY provisioned for the Polsia AI proxy in the deployed app.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. For AI output, the deployed app needs POLSIA_API_KEY provisioned for the Polsia AI proxy.
Compares the supplied document list with a configured checklist and reports present and missing items for new patient intake automation.
How New Patient Intake Automation works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Documents
3
Create the resultReports whether required documents are complete and lists any that are missing.
Inputs: JSON input with records containing: id, approved, documents. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. A configured requiredItems document checklist.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Checks supplied records against configured eligible season or due date rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Automated Recall Email Campaigns works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied records against configured availability source rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Appointment Reminder Emails works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied records against configured audience eligibility rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Post-Visit Follow-Up Sequences works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Creates a response draft from customer-approved positive or negative response text using the supplied rating; a person reviews it before use.
How Google Review Response Automation works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Rating
Customer feedback
3
Create the resultCreates a response draft from the configured positive or negative text.
Inputs: JSON input with records containing: id, approved, rating, reviewText. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Customer-approved positive and negative response templates.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Checks supplied records against configured eligible season or due date rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Review Request Campaigns works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Summarizes supplied reputation dashboard & reporting records with status counts and optional configured totals or groups.
How Reputation Dashboard & Reporting works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Required fields
Configured rules
3
Create the resultSummarizes record status counts and any configured totals.
Inputs: JSON input with records containing: id, approved. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Uses the Polsia AI proxy to prepare a patient newsletter & education emails draft from supplied approved facts; the named reviewer checks it before use.
How Patient Newsletter & Education Emails works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Source facts
3
Create the resultCreates an AI draft using the supplied source facts.
Inputs: JSON input with records containing: id, approved, approvedFacts. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. POLSIA_API_KEY provisioned for the Polsia AI proxy in the deployed app.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. For AI output, the deployed app needs POLSIA_API_KEY provisioned for the Polsia AI proxy.
Uses the Polsia AI proxy to prepare a blog & website content generation draft from supplied approved facts; the named reviewer checks it before use.
How Blog & Website Content Generation works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Source facts
3
Create the resultCreates an AI draft using the supplied source facts.
Inputs: JSON input with records containing: id, approved, approvedFacts. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. POLSIA_API_KEY provisioned for the Polsia AI proxy in the deployed app.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. For AI output, the deployed app needs POLSIA_API_KEY provisioned for the Polsia AI proxy.
Summarizes supplied lead tracking & inquiry reporting records with status counts and optional configured totals or groups.
How Lead Tracking & Inquiry Reporting works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Required fields
Configured rules
3
Create the resultSummarizes record status counts and any configured totals.
Inputs: JSON input with records containing: id, approved. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Checks supplied automated client inquiry response records against configured required fields and business rules, then returns a rule-based result and assigned reviewer.
How Automated Client Inquiry Response works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultReturns a rule result and the assigned owner.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Uses the Polsia AI proxy to answer a supplied question from configured approved knowledge entries; unanswered questions are marked for staff response.
How 24/7 Practice Area FAQ Chatbot works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Question
3
Create the resultCreates an AI answer from the configured knowledge base, or flags unanswered questions.
Inputs: JSON input with records containing: id, approved, question. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. An approved knowledgeBase with answer entries. POLSIA_API_KEY provisioned for the Polsia AI proxy in the deployed app.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. For AI output, the deployed app needs POLSIA_API_KEY provisioned for the Polsia AI proxy.
Checks supplied records against configured audience eligibility rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Instant Inquiry Follow-Up Emails works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Compares the supplied document list with a configured checklist and reports present and missing items for new client intake form automation.
How New Client Intake Form Automation works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Documents
3
Create the resultReports whether required documents are complete and lists any that are missing.
Inputs: JSON input with records containing: id, approved, documents. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. A configured requiredItems document checklist.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Checks supplied records against configured audience eligibility rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Consultation Reminder Email Sequences works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied records against configured audience eligibility rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Post-Consultation Follow-Up Sequences works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Creates a response draft from customer-approved positive or negative response text using the supplied rating; a person reviews it before use.
How Google Review Response Automation works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Rating
Customer feedback
3
Create the resultCreates a response draft from the configured positive or negative text.
Inputs: JSON input with records containing: id, approved, rating, reviewText. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Customer-approved positive and negative response templates.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Checks supplied records against configured eligible season or due date rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Review Request Email Campaigns works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Summarizes supplied reputation dashboard & reporting records with status counts and optional configured totals or groups.
How Reputation Dashboard & Reporting works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Required fields
Configured rules
3
Create the resultSummarizes record status counts and any configured totals.
Inputs: JSON input with records containing: id, approved. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Uses the Polsia AI proxy to prepare a legal blog & educational content draft from supplied approved facts; the named reviewer checks it before use.
How Legal Blog & Educational Content works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Source facts
3
Create the resultCreates an AI draft using the supplied source facts.
Inputs: JSON input with records containing: id, approved, approvedFacts. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. POLSIA_API_KEY provisioned for the Polsia AI proxy in the deployed app.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. For AI output, the deployed app needs POLSIA_API_KEY provisioned for the Polsia AI proxy.
Uses the Polsia AI proxy to prepare a client newsletter & email campaigns draft from supplied approved facts; the named reviewer checks it before use.
How Client Newsletter & Email Campaigns works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Source facts
3
Create the resultCreates an AI draft using the supplied source facts.
Inputs: JSON input with records containing: id, approved, approvedFacts. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. POLSIA_API_KEY provisioned for the Polsia AI proxy in the deployed app.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. For AI output, the deployed app needs POLSIA_API_KEY provisioned for the Polsia AI proxy.
Summarizes supplied lead tracking & inquiry reporting records with status counts and optional configured totals or groups.
How Lead Tracking & Inquiry Reporting works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Required fields
Configured rules
3
Create the resultSummarizes record status counts and any configured totals.
Inputs: JSON input with records containing: id, approved. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Checks supplied automated lead inquiry response records against configured required fields and business rules, then returns a rule-based result and assigned reviewer.
How Automated Lead Inquiry Response works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultReturns a rule result and the assigned owner.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Uses the Polsia AI proxy to answer a supplied question from configured approved knowledge entries; unanswered questions are marked for staff response.
How 24/7 Property & Neighborhood Chatbot works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Question
3
Create the resultCreates an AI answer from the configured knowledge base, or flags unanswered questions.
Inputs: JSON input with records containing: id, approved, question. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. An approved knowledgeBase with answer entries. POLSIA_API_KEY provisioned for the Polsia AI proxy in the deployed app.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. For AI output, the deployed app needs POLSIA_API_KEY provisioned for the Polsia AI proxy.
Checks supplied records against configured audience eligibility rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Instant Lead Follow-Up Emails works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied records against configured availability source rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Showing Confirmation & Reminder Emails works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied records against configured availability source rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Post-Showing Follow-Up Sequences works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Compares the supplied document list with a configured checklist and reports present and missing items for rental application intake automation.
How Rental Application Intake Automation works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Documents
3
Create the resultReports whether required documents are complete and lists any that are missing.
Inputs: JSON input with records containing: id, approved, documents. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. A configured requiredItems document checklist.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Creates a response draft from customer-approved positive or negative response text using the supplied rating; a person reviews it before use.
How Google Review Response Automation works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Rating
Customer feedback
3
Create the resultCreates a response draft from the configured positive or negative text.
Inputs: JSON input with records containing: id, approved, rating, reviewText. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Customer-approved positive and negative response templates.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Checks supplied records against configured eligible season or due date rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Review Request Email Campaigns works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Summarizes supplied reputation dashboard & reporting records with status counts and optional configured totals or groups.
How Reputation Dashboard & Reporting works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Required fields
Configured rules
3
Create the resultSummarizes record status counts and any configured totals.
Inputs: JSON input with records containing: id, approved. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Uses the Polsia AI proxy to prepare a property listing description generation draft from supplied approved facts; the named reviewer checks it before use.
How Property Listing Description Generation works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Source facts
3
Create the resultCreates an AI draft using the supplied source facts.
Inputs: JSON input with records containing: id, approved, approvedFacts. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. POLSIA_API_KEY provisioned for the Polsia AI proxy in the deployed app.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. For AI output, the deployed app needs POLSIA_API_KEY provisioned for the Polsia AI proxy.
Uses the Polsia AI proxy to prepare a email newsletters & market updates draft from supplied approved facts; the named reviewer checks it before use.
How Email Newsletters & Market Updates works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Source facts
3
Create the resultCreates an AI draft using the supplied source facts.
Inputs: JSON input with records containing: id, approved, approvedFacts. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. POLSIA_API_KEY provisioned for the Polsia AI proxy in the deployed app.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. For AI output, the deployed app needs POLSIA_API_KEY provisioned for the Polsia AI proxy.
Summarizes supplied lead tracking & pipeline reporting records with status counts and optional configured totals or groups.
How Lead Tracking & Pipeline Reporting works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Required fields
Configured rules
3
Create the resultSummarizes record status counts and any configured totals.
Inputs: JSON input with records containing: id, approved. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Checks supplied records against configured audience eligibility rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Immediate Lead Follow-Up Sequence works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied records against configured eligible season or due date rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Lead Qualification Drip Campaigns works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied records against configured eligible season or due date rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Re-Engagement Campaigns for Stale Leads works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Uses the Polsia AI proxy to prepare a ai-drafted client newsletters draft from supplied approved facts; the named reviewer checks it before use.
How AI-Drafted Client Newsletters works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Source facts
3
Create the resultCreates an AI draft using the supplied source facts.
Inputs: JSON input with records containing: id, approved, approvedFacts. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. POLSIA_API_KEY provisioned for the Polsia AI proxy in the deployed app.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. For AI output, the deployed app needs POLSIA_API_KEY provisioned for the Polsia AI proxy.
Checks supplied records against configured audience eligibility rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Life Event & Milestone Touchpoints works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied records against configured business rules and prepares a review & referral request automation follow-up result.
How Review & Referral Request Automation works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based follow-up draft for each eligible record.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Compares the supplied document list with a configured checklist and reports present and missing items for document collection sequences.
How Document Collection Sequences works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Documents
3
Create the resultReports whether required documents are complete and lists any that are missing.
Inputs: JSON input with records containing: id, approved, documents. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. A configured requiredItems document checklist.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Checks supplied records against configured audience eligibility rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Onboarding Progress Emails works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied records against configured record status rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Welcome Sequences for New Clients works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied records against configured eligible season or due date rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How 90-Day Renewal Reminder Campaigns works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied records against configured eligible season or due date rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Annual Review Scheduling Campaigns works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied records against configured eligible season or due date rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Win-Back Campaigns for Lapsed Clients works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Government and compliance · Runnable code template
FOIA Request Triage & Routing
Checks supplied records against a configured evidence checklist, reports missing items, and returns a review-owner handoff for foia request triage & routing.
How FOIA Request Triage & Routing works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Evidence
3
Create the resultReports whether required evidence is complete and lists any that is missing.
Inputs: JSON input with records containing: id, approved, evidence. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. A configured requiredItems evidence checklist.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Government and compliance · Runnable code template
Automated Document Search & Compilation
Compares the supplied document list with a configured checklist and reports present and missing items for automated document search & compilation.
How Automated Document Search & Compilation works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Documents
3
Create the resultReports whether required documents are complete and lists any that are missing.
Inputs: JSON input with records containing: id, approved, documents. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. A configured requiredItems document checklist.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Government and compliance · Runnable code template
Response Draft Generation
Uses the Polsia AI proxy to prepare a response draft generation draft from supplied approved facts; the named reviewer checks it before use.
How Response Draft Generation works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Source facts
3
Create the resultCreates an AI draft using the supplied source facts.
Inputs: JSON input with records containing: id, approved, approvedFacts. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. POLSIA_API_KEY provisioned for the Polsia AI proxy in the deployed app.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. For AI output, the deployed app needs POLSIA_API_KEY provisioned for the Polsia AI proxy.
Government and compliance · Runnable code template
Continuous Compliance Evidence Collection
Checks supplied records against a configured evidence checklist, reports missing items, and returns a review-owner handoff for continuous compliance evidence collection.
How Continuous Compliance Evidence Collection works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Evidence
3
Create the resultReports whether required evidence is complete and lists any that is missing.
Inputs: JSON input with records containing: id, approved, evidence. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. A configured requiredItems evidence checklist.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Government and compliance · Runnable code template
Grant & Contract Performance Reporting
Summarizes supplied grant & contract performance reporting records with status counts and optional configured totals or groups.
How Grant & Contract Performance Reporting works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Required fields
Configured rules
3
Create the resultSummarizes record status counts and any configured totals.
Inputs: JSON input with records containing: id, approved. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Government and compliance · Runnable code template
Regulatory Change Monitoring
Checks supplied records against a configured evidence checklist, reports missing items, and returns a review-owner handoff for regulatory change monitoring.
How Regulatory Change Monitoring works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Evidence
3
Create the resultReports whether required evidence is complete and lists any that is missing.
Inputs: JSON input with records containing: id, approved, evidence. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. A configured requiredItems evidence checklist.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Government and compliance · Runnable code template
RFP & Bid Opportunity Monitoring
Checks supplied records against a configured evidence checklist, reports missing items, and returns a review-owner handoff for rfp & bid opportunity monitoring.
How RFP & Bid Opportunity Monitoring works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Evidence
3
Create the resultReports whether required evidence is complete and lists any that is missing.
Inputs: JSON input with records containing: id, approved, evidence. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. A configured requiredItems evidence checklist.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Government and compliance · Runnable code template
Proposal Section Drafting
Uses the Polsia AI proxy to prepare a proposal section drafting draft from supplied approved facts; the named reviewer checks it before use.
How Proposal Section Drafting works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Source facts
3
Create the resultCreates an AI draft using the supplied source facts.
Inputs: JSON input with records containing: id, approved, approvedFacts. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. POLSIA_API_KEY provisioned for the Polsia AI proxy in the deployed app.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. For AI output, the deployed app needs POLSIA_API_KEY provisioned for the Polsia AI proxy.
Government and compliance · Runnable code template
Deadline & Deliverable Tracking
Checks supplied records against a configured evidence checklist, reports missing items, and returns a review-owner handoff for deadline & deliverable tracking.
How Deadline & Deliverable Tracking works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Evidence
3
Create the resultReports whether required evidence is complete and lists any that is missing.
Inputs: JSON input with records containing: id, approved, evidence. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. A configured requiredItems evidence checklist.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Government and compliance · Runnable code template
Audit-Ready Evidence Management
Checks supplied records against a configured evidence checklist, reports missing items, and returns a review-owner handoff for audit-ready evidence management.
How Audit-Ready Evidence Management works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Evidence
3
Create the resultReports whether required evidence is complete and lists any that is missing.
Inputs: JSON input with records containing: id, approved, evidence. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. A configured requiredItems evidence checklist.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Government and compliance · Runnable code template
Compliance Gap Detection
Checks supplied records against a configured evidence checklist, reports missing items, and returns a review-owner handoff for compliance gap detection.
How Compliance Gap Detection works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Evidence
3
Create the resultReports whether required evidence is complete and lists any that is missing.
Inputs: JSON input with records containing: id, approved, evidence. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. A configured requiredItems evidence checklist.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Government and compliance · Runnable code template
Policy Review & Update Automation
Checks supplied records against a configured evidence checklist, reports missing items, and returns a review-owner handoff for policy review & update automation.
How Policy Review & Update Automation works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Evidence
3
Create the resultReports whether required evidence is complete and lists any that is missing.
Inputs: JSON input with records containing: id, approved, evidence. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. A configured requiredItems evidence checklist.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Restaurants and hospitality · Runnable code template
No-Show Reduction Sequences
Checks supplied records against configured record status rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How No-Show Reduction Sequences works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Restaurants and hospitality · Runnable code template
Special Occasion Upsells
Checks supplied records against configured audience eligibility rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Special Occasion Upsells works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Restaurants and hospitality · Runnable code template
Waitlist Fill Automation
Checks supplied waitlist fill automation records and returns the first supplied available option when present; it does not book or change a schedule.
How Waitlist Fill Automation works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Available times
3
Create the resultReturns the first supplied available time; it does not make a booking.
Inputs: JSON input with records containing: id, approved, availableSlots. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Restaurants and hospitality · Runnable code template
Post-Visit Review Requests
Checks supplied records against configured completed-work status rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Post-Visit Review Requests works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Restaurants and hospitality · Runnable code template
Negative Feedback Interception
Creates a response draft from customer-approved positive or negative response text using the supplied rating; a person reviews it before use.
How Negative Feedback Interception works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Rating
Customer feedback
3
Create the resultCreates a response draft from the configured positive or negative text.
Inputs: JSON input with records containing: id, approved, rating, reviewText. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Customer-approved positive and negative response templates.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Restaurants and hospitality · Runnable code template
Review Response Drafting
Uses the Polsia AI proxy to prepare a review response drafting draft from supplied approved facts; the named reviewer checks it before use.
How Review Response Drafting works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Source facts
3
Create the resultCreates an AI draft using the supplied source facts.
Inputs: JSON input with records containing: id, approved, approvedFacts. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. POLSIA_API_KEY provisioned for the Polsia AI proxy in the deployed app.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. For AI output, the deployed app needs POLSIA_API_KEY provisioned for the Polsia AI proxy.
Restaurants and hospitality · Runnable code template
Post-Visit Re-Engagement Flows
Checks supplied records against configured audience eligibility rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Post-Visit Re-Engagement Flows works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Restaurants and hospitality · Runnable code template
Birthday & Anniversary Campaigns
Checks supplied records against configured eligible season or due date rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Birthday & Anniversary Campaigns works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Restaurants and hospitality · Runnable code template
Lapsed Guest Win-Back Sequences
Checks supplied records against configured audience eligibility rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Lapsed Guest Win-Back Sequences works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Restaurants and hospitality · Runnable code template
Multi-Platform Order Consolidation
Checks supplied multi-platform order consolidation records against configured rules and returns a priority and assigned-owner handoff.
How Multi-Platform Order Consolidation works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultReturns priority, rule result, and assigned owner.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Restaurants and hospitality · Runnable code template
Promotional Campaign Automation
Checks supplied records against configured eligible season or due date rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Promotional Campaign Automation works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Restaurants and hospitality · Runnable code template
Hotel Pre-Arrival & Upsell Flows
Checks supplied records against configured audience eligibility rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Hotel Pre-Arrival & Upsell Flows works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied records against configured item or order identifier rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Cart Abandonment Recovery works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied records against configured audience eligibility rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Post-Purchase Upsell Flows works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Uses the Polsia AI proxy to prepare a ai product description generation draft from supplied approved facts; the named reviewer checks it before use.
How AI Product Description Generation works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Source facts
3
Create the resultCreates an AI draft using the supplied source facts.
Inputs: JSON input with records containing: id, approved, approvedFacts. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. POLSIA_API_KEY provisioned for the Polsia AI proxy in the deployed app.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. For AI output, the deployed app needs POLSIA_API_KEY provisioned for the Polsia AI proxy.
Uses the Polsia AI proxy to answer a supplied question from configured approved knowledge entries; unanswered questions are marked for staff response.
How AI Support Chatbot works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Question
3
Create the resultCreates an AI answer from the configured knowledge base, or flags unanswered questions.
Inputs: JSON input with records containing: id, approved, question. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. An approved knowledgeBase with answer entries. POLSIA_API_KEY provisioned for the Polsia AI proxy in the deployed app.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. For AI output, the deployed app needs POLSIA_API_KEY provisioned for the Polsia AI proxy.
Checks a supplied return request against the configured return window and required evidence, then flags it for human approval; it does not issue refunds or change orders.
How Automated Returns Processing works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Order ID
Days since purchase
Item condition
Evidence
3
Create the resultReports whether the return meets the configured window and evidence rules. It does not issue a refund.
Inputs: JSON input with records containing: id, approved, orderId, daysSincePurchase, itemCondition, evidence. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. A configured returnWindowDays and requiredItems evidence checklist.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Checks supplied records against configured item or order identifier rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Order Status Notification Flows works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Compares a supplied quantity with a configured threshold and returns a review recommendation for low stock alert workflows; it does not change stock or place orders.
How Low Stock Alert Workflows works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Quantity
3
Create the resultReports stock against the configured quantity threshold and gives a replenishment recommendation.
Inputs: JSON input with records containing: id, approved, quantity. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. A numeric business-approved threshold.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Summarizes supplied demand forecasting alerts records with status counts and optional configured totals or groups.
How Demand Forecasting Alerts works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Required fields
Configured rules
3
Create the resultSummarizes record status counts and any configured totals.
Inputs: JSON input with records containing: id, approved. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Compares a supplied quantity with a configured threshold and returns a review recommendation for back-in-stock notification sequences; it does not change stock or place orders.
How Back-in-Stock Notification Sequences works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Quantity
3
Create the resultReports stock against the configured quantity threshold and gives a replenishment recommendation.
Inputs: JSON input with records containing: id, approved, quantity. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. A numeric business-approved threshold.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.
Checks supplied records against configured completed-work status rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Review Request Automation works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied records against configured eligible season or due date rules and prepares one message draft per eligible record. Optional email delivery sends one configured message only after explicit enablement, recipient permission, and human approval.
How Win-Back Campaigns for Lapsed Customers works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based message draft for each eligible record.
4
Send emailWhen enabled, sends the configured message to valid, opted-in recipients whose records pass the required send checks; skips opt-outs.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed; optional email also needs a valid recipient and explicit permission.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection. Optional one-message delivery requires config.sendEmails: true, a configured subject and body, valid email, emailConsent: true, humanApproved: true, and the deployed Polsia email proxy.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer. Optional one-message email delivery requires the deployed Polsia email proxy, POLSIA_API_KEY, POLSIA_COMPANY_EMAIL, valid recipient addresses, explicit email consent, human approval, and an approved subject and body.
Checks supplied records against configured business rules and prepares a subscription churn intervention follow-up result.
How Subscription Churn Intervention works, from supplied input through the workflow result.
1
Supply inputProvide records with the required fields.
2
Check the rulesChecks required fields, duplicate records if set up, and configured rules.
Status
3
Create the resultCreates a rule-based follow-up draft for each eligible record.
Inputs: JSON input with records containing: id, approved, status. Use only customer-approved data; set duplicateKey to an approved unique field when duplicate detection is needed.
Configuration: Node.js 18 or newer. A named reviewer and business-approved required fields and rules; duplicateKey is optional and enables duplicate detection.
Before running: Node.js 18 or newer. A local JSON export or manually prepared JSON input. Customer-approved fields and rules plus a named reviewer.