john9724Q: Scheduling emails for future
Questions:
I plan to use Predimail to track the progress of custom 6-12 month manufacturing process and get updates. For each job, I have key dates to send reminders, ask progress and once a milestone is reached, update the database and schedule future emails based on that. Knowledgebase could be the calculated reminder emails but those dates change based on email exchanges. Based on this:
1) Does predimail schedule future emails at selected dates
2) Can predimail read the email exchanges with each manufacturer / email sender to maintain context?
3) Can it connect to a database in knowledgebase to update information based on email exchanges?
4) Can knowledgebase be Google sheets or a database that gets new rows based on new jobs for custom manufacturing and triggers the future emails and dates in Predimail?
Thank you
Admin_Predimail
Edited Jul 1, 2026A: Hi, and thanks for laying out your use case so clearly — it helps me give you a straight answer.
Quick framing first: PREDIMAIL is an inbound mailbox automation tool. It reads your incoming email, classifies and routes it, and drafts (or sends) replies grounded in a knowledge base you control. It's not a proactive scheduler or a workflow/state engine, so let me map that against your four points honestly.
1) Does PREDIMAIL schedule future emails at selected dates?
No. PREDIMAIL acts in response to incoming mail — it doesn't run time-based triggers that send scheduled emails on future dates. The date-driven, "remind on day X" logic you're describing would need to live in a scheduling/orchestration layer, not in PREDIMAIL.
2) Can it read the email exchanges with each manufacturer to maintain context?
This is where PREDIMAIL fits well. The knowledge base can ingest your files, URLs, and the emails exchanged over a date range you select — so past correspondence with a given manufacturer can be used as context when it classifies and drafts replies. So it can understand and respond within an ongoing exchange using that history.
3) Can it connect to a database in the knowledge base and update it based on email exchanges?
No. The knowledge base is a source PREDIMAIL reads from to generate replies — it doesn't write structured updates back into an external database. So the "update the record when a milestone is reached" step would need to happen in your own system.
4) Can the knowledge base be a Google Sheet / database that gets new rows per job and triggers future emails and dates?
Not today. Knowledge base sources are files, URLs, and emails — there's no Google Sheets/database connector, and no engine that turns new rows into scheduled email triggers.
How PREDIMAIL could realistically fit your setup
The state and scheduling — jobs, key dates, milestones, recalculated reminders — would live in your database plus an orchestration tool (e.g. Make, n8n, Zapier). PREDIMAIL would handle the language side: reading the manufacturer's incoming replies, understanding progress, and drafting the outgoing updates using your knowledge base. That combination plays to its strengths without asking it to be something it isn't.
I'd rather be upfront so you don't buy it expecting the scheduling/database automation — that part isn't what PREDIMAIL does. If the reply-understanding-and-drafting piece is valuable to you on its own, it's a strong fit; happy to talk through how you'd wire it up.