Automated Influitive Reward Fulfilment Queue
Every morning, WebRun opens Influitive, reads the reward redemptions advocates have claimed since the last run, records each one in Airtable with the advocate, the reward, and the points spent, and writes a short Notion brief listing who is owed what today and which claims have been waiting longest.
How do I keep on top of advocate reward redemptions every day?
WebRun opens Influitive every morning and reads the rewards your advocates have claimed. It records each claim in Airtable with the advocate, reward, and points spent, then writes a Notion brief of who is owed what today, so a customer who earned a reward is not still waiting next week.
- Every claim has an owner the morning it is made
- The oldest claims sit at the top instead of getting buried
- Claims past your promised turnaround are called out by name
Built for advocacy managers · customer marketing teams · community managers · customer success
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
influitive.comin a real browser with your saved login - no setup, no API keys. -
1
Influitive - read claimed reward redemptions
influitive.com
WebRun opens Influitive to read claimed reward redemptions. - Open Influitive and go to the reward redemptions list
- Capture every claim made since the last run with the advocate, the reward, and the points spent
- Note the date claimed and the current fulfilment status
- Check the challenges that earned those points so the context travels with the claim
- Skip claims already marked fulfilled
Done when Every outstanding redemption is captured with its advocate, reward, and claim date.
-
2
Airtable - build the fulfilment queue
airtable.com
WebRun opens Airtable to build the fulfilment queue. - Add a record per claim to your fulfilment base
- Fill in the advocate, the reward, the points spent, the claim date, and the days waiting
- Assign each record to whoever fulfils that reward type
- Update records from earlier runs whose status has changed in Influitive
Done when The fulfilment base holds every open claim once, with an owner and an age.
-
3
Notion - brief who is owed what today
notion.so
WebRun opens Notion to brief who is owed what today. - Write today's brief on your advocacy page: how many claims are open and their total value in points
- List the oldest claims first with the advocate and reward named
- Call out anything past the turnaround you promise advocates
- Leave the sending of any reward to a human. WebRun queues, it never fulfils or emails the advocate
Done when The advocacy page holds today's brief with the oldest claims at the top.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it send rewards or gift cards on its own?
No. WebRun builds the queue and names the owner. Actually issuing a reward, spending money, or emailing the advocate stays a human step, so nothing of value leaves without approval.
How does it stop a claim being fulfilled twice?
It reads the live fulfilment status in Influitive each morning and matches against records already in Airtable, so a claim your team has closed is updated rather than re-queued.
Can different rewards go to different people?
Yes. You map reward types to owners once, and WebRun assigns each Airtable record to the right person, so gift cards and swag do not land in the same pile.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.