Phillip_Wild

Hmmm....good question re volume. I would guess...maybe 1,000? I could batch them so it was lower if that helps.An intermediate webhook could work - maybe through something like Zapier?

Hi NikkiCould you clarify for me? When you say "people to not get dupes" but also "qualify for a second time through", isn't that the same thing? If you could qualify again, wouldn't that be a duplicate send?

Ah well. Time to bite the bullet I think. Folder level token, then update every subject line manually to be that token. At least it's one update if it ever needs changing again.Ah, to have set this up when I was older and a bit wiser....Thanks for your help all.

Would be perfect....but unfortunately all of these emails were set up with hardcoded subject lines So unless I go through and replace them all with tokens (which is future-proofed, but still time-consuming) I'm out of luck...

Hi GrégoireUnfortunately that's the original endpoint I was using, which gives me the error above....so it seems there is no way to update the subject line unless the emails are in a template then? That other endpoint is useful, but without the ability to modify subject lines via API I can't solve m...

Thanks Grégoire! No I wasn't aware of that endpoint....seems quite handy! Forgive my naivety...but is it possible to update subject lines using that endpoint? Updating the HTML is useful, but in this particular circumstance I need to replace subject lines.As a secondary question, that endpoint requi...

I think Mike's suggestion is the cleanest way to accomplish this. We have something a little similar whereby before each cast we change program statuses for everyone who shouldn't receive particular emails. After the cast, we change it back for those who didn't receive it. We use this to ensure that...

Perfect. Thanks!