Does GetResponse Remember Between Runs? Vilix AI Remembers the Work It Forgets
A GetResponse contact can sit in your account with its tags, custom fields, and a 1 to 5 engagement score, and the next workflow run still starts knowing nothing about the work already done on it.
AI Stella and Liam are AI hosts with AI-generated voices. About our AI hosts
Key takeaways
- A GetResponse contact keeps only current state: tags currently assigned, custom fields currently stored, and the score right now, with every later write replacing the earlier value.
- A tag records that a label applies, never why it was applied. The engagement score is just 1 to 5 and cannot explain itself, so the reason behind a decision is gone even though the label stays.
- Workflows share no working state: a second workflow sees only what the first one wrote back, a tag, a field, a list move, or a score change, so an unwritten conclusion is unrecoverable.
- Vilix AI fixes the missing half: get_context at run start loads who was already reviewed and every decision made, and save_turn at the end saves the reasoning and failures back with source labels and newest wins, over MCP with zero infrastructure.
Show notes
A GetResponse contact can sit in your account with its tags, custom fields, and a 1 to 5 engagement score, and the next workflow run still starts knowing nothing about the work already done on it. In this episode of Agentic Pod, Liam and Stella break down what a contact record actually keeps: the tags currently assigned, the custom fields currently stored, and the score currently on the contact, with every later write replacing the earlier value. Inside one run the workflow branches on that record, and a second workflow sees only what the first one wrote back, a tag, a field, a list move, or a score change. Vilix AI is the memory layer that fixes that missing half: get_context at run start loads what was already decided, and save_turn at the end saves the reasoning back for every tool in the workflow.
What we cover:
- Custom fields are current state only: name, plan, signup source, or preference, and the contact card shows the latest value, never the history
- Tags accumulate until removed, but a tag records that a label applies, never why it was applied or what was decided before it
- Scores branch the path: workflow scoring adds or subtracts points, and engagement scoring is a separate 1 to 5 read that cannot explain itself
- Inside one run: conditions admit a contact, actions send, tag, score, copy, move, or remove, and Wait elements resume the contact, which is progress, not memory
- Between workflows: no shared working state, so an unwritten conclusion is unrecoverable for the next workflow
- The weekly re-engagement gap: the next run cannot see why a contact was skipped, which angle was tried and rejected, or what was planned next
- How Vilix AI fixes each pain: get_context, save_turn with source labels, failures saved, newest wins, projects, project rules, user rules, skills, and the agent inbox, over MCP with zero infrastructure
Chapters
Questions answered in this episode
Does GetResponse remember between runs?
The contact record remembers: tags, custom fields and the score, all at their latest values. It does not remember the work: why a contact was skipped, which angle was tried and rejected, or what was planned next.
What do GetResponse custom fields keep?
Only the latest value, such as name, plan, signup source or a preference. A later write replaces the earlier one, so the history of values is never shown on the contact card.
Why does a weekly re-engagement job repeat decisions?
The next run sees only the tags, fields and scores written back. With no note on why a contact was skipped or which angle was rejected, it can repeat a decision that was already thrown out.
How does Vilix AI help GetResponse workflows?
The workflow calls get_context before reviewing contacts to load who was already reviewed and every decision made, then save_turn after the run to store decisions and failures with a source label, shared over MCP with every connected workflow.
Links & resources
Full transcript
Intro
Hey hey hey, welcome to Agentic Pod! I'm Liam.
And I'm Stella! Quick check. Your contact is still in GetResponse today, right?
Yes. And the engagement score on that contact is just 1 to 5.
1 to 5 sounds like it knows the person.
It knows the record, not the work. Vilix AI is how your workflow remembers its work.
Wait. The contact survives, but the work on it does not?
Exactly that. By the end you will know what a contact keeps, and what it loses.
What a contact actually keeps
Okay, start simple. What does GetResponse actually store?
The contact record. Tags currently assigned, custom fields currently stored, and the score right now.
Custom fields are like, what, name, plan, signup source?
Exactly. Name, plan, signup source, a preference. A form, an import, an API call, or a workflow sets them.
And a later write just replaces the old value?
It replaces it. The contact card shows the latest value, not the history of values.
Tags are different though, right? They pile up.
Tags accumulate until removed. A product interest, a customer status, who started a workflow.
But a tag never says why it was added?
Never. You just described my whole filing system, and I feel attacked.
Good. So the label is there, the reason is gone. Where is the catch?
Inside one run, and between two workflows
Inside 1 run, things look tidy. A condition admits a contact. Actions send, tag, score, copy, move.
And conditions branch on the record. Tag assigned, field changed, score given.
Right. Wait elements hold the contact, and the workflow resumes it at the right element.
That resume feels like memory though.
It is workflow progress, not run memory. Once the contact exits, no working notes stay.
And a second workflow sees even less?
Way less. Workflows share no working state. The next 1 sees only what was written back.
A tag, a field, a list move, a score change. That is the whole handoff?
That is the whole handoff. If nobody wrote the conclusion down, it is gone. Vilix AI keeps that half.
Hold on. When does this actually bite in real work?
The weekly job that repeats itself
A weekly re-engagement job. An agent reviews quiet contacts, and picks who gets a new angle.
And who should be left alone. That part matters.
Next week, GetResponse shows the tags, fields, and scores written back. Nothing else.
No note on why a contact was skipped?
No note. No angle already tried and rejected. No plan for what comes next.
So the next run can repeat a decision that was already thrown out?
Word for word. Same in lead qualification, and onboarding across several workflows.
And forcing reasons into fields just makes it worse?
Fields multiply, values get overwritten, only the latest conclusion survives. Vilix AI fixes that gap.
Alright, Liam. No more tour. Show me the actual fix.
The Vilix AI fix and the verdict
Step 1. At run start, the job calls get_context in Vilix AI. That loads who was reviewed, and every decision made.
Full history, not just the latest field value?
Full conversation history, not just facts. Reasoning and failures too. Failures save in Vilix AI, so the next run skips them.
And at the end of the run?
Step 2. The job calls save_turn in Vilix AI, with a source label. Newest save wins.
Where do the standing rules live?
In Vilix AI, as projects, project rules, and user rules. Skills hold repeat workflows. The agent inbox holds next agent notes.
And the chat tool checking the draft, in a totally different app?
Same Vilix AI memory, over MCP. The workflow, the agent, every tool, all read the same past.
Do I host a database or a server for that?
No. Vilix AI is cloud hosted, zero infrastructure to run. One Vilix AI account per client, so memories never mix.
Price of admission?
Vilix AI has a free forever plan, and a 7 day Pro trial, no credit card. Export or delete anytime.
My verdict: GetResponse remembers the contact perfectly. It remembers the work not at all.
Same. Keep GetResponse for the record. Let Vilix AI carry the work. Blog and guide are linked below. Does your weekly job repeat decisions? Tell us below. See you next time!