Generating mass lists and checking for duplicates/remove mass update list

You can handle this by putting a check before creating a new activity. 

1. Your automation runs through each contact in the event’s contact list.

2. Before creating a new activity (invitation), it searches the Activities table for a record where the contact AND the event match.

3. If a match is found, the automation skips that contact. If no match is found, it creates the invitation.

Taha, Views And Bases

Sigh yeah this is always a bit of a headache.  I’ve got two workarounds for this, one that uses up a lot of automation runs but is easier to wrap ones head around, and another that uses fewer but is more convoluted

The easy one (which I’ve set up here for you to check out with the automations) involves creating a formula field that’ll output a unique value per contact that’s been added by combining it with the event name, so something like this:

And you then get the automation to paste that text value into the Invitations field.  This will then either link to an existing record with that primary field value, or create a new one:

After that you’ll have another automation that’ll help you link the invitations to each contact, and we do that by:

1. Creating a formula field to get the contacts name
2. Using an automation to paste that into the linked field to Contacts

Ideally you’d want to use the Contact record ID instead of the name too, but I wanted to keep it clear for this example

Let me know if you want the version that uses fewer automation runs, running a bit late and don’t have the time to write that one out right now sorry!

I always try to start with ​@TheTimeSavingCo (Adam’s) approach before going full automation with this. Using the right IDs for linked records can resolve so many potential duplication issues.