You can also use the Admin - Settings > Application - “Incoming Action Set: (Add)” to run actions on any coming through API, not just that Company’s endpoint.
You could have it run based on criteria, but none of the populated info would be usable in this case, I think.
You can also use the Admin - Settings > Application - “Incoming Action Set: (Add)” to run actions on any coming through API, not just that Company’s endpoint.
Thanks for the idea - I thought this was going to be the fix! But unfortunately and for some unknown reason, contacts created by this 3rd party via the API aren’t picked up by the action set.
I’m even running the action set with no criteria, so theoretically all contacts created via API should be triggering the action set.
Interestingly, where contacts are being created via other API integrations I am using (Zapier for example), your solution works just fine.
I also have another 3rd party partner that sends us leads via their API integration - but this also doesn’t trigger the action set either.
I’ve had to refer it to support but they don’t know what’s wrong at the moment.
The Admin - Settings > Application > API Key should be the one that triggers Actions on incoming API Contacts. I might have to run a few tests to see if maybe some contact creation methods work and some don’t.
For anyone interested, I couldn’t fix this in IFS so am using Zapier to add a tag each time a new contact is created.
Luckily the the 3rd party preceeds each contact name they send over with “site visitor from…” so i was able to use this as a condition in Zapier to make sure only relevant contacts were tagged (i.e. if contact name begins with “site visitor from”, add tag X).