Connect Agillic

With the Agillic integration, everyone who signs up is created or updated as a recipient in Agillic. Agillic doesn't use lists here: recipients are added to your Agillic data, and you build your target groups in Agillic.

What you need

• An Agillic account on Agillic's European platform, and a user who can create API keys (usually an administrator).

Step 1: Create an API key in Agillic

1. In Agillic, open Settings and find the API keys (API credentials).
2. Create a new key, and give it a name you recognise, for example "Scratcher".
3. Copy the Developer key (also called API key) and the Secret. The secret is only shown once.

Permissions the key needs

Scratcher uses the key to read your person data fields, find recipients by email, and create and update recipients. If Agillic lets you limit the key, it needs read and write access to recipients and read access to person data. No other access is needed.

Step 2: Connect Agillic to Scratcher

1. In Scratcher, go to Settings > Integrations and click Agillic.
2. Paste the Developer key and the Secret.
3. Click Install integration. Scratcher logs in to Agillic to check them.

Step 3: Turn it on in a campaign

1. In the editor, go to Connect > Integrations > Agillic and click Activate.
2. If you have connected more than one account, choose it under Select account.
3. Under Field mappings, match each Scratcher field to an Agillic person data field.
4. Under Unique email field, choose the Agillic field you use for email: "Choose the field in Agillic that you use for email (ensure it is unique in Agillic as well)". Only unique text fields are listed. If you leave it empty, Scratcher uses the field EMAIL.
5. Under Filter by permissions (optional), choose your marketing consent checkbox, so only people who said yes are sent.
6. Click Save, and then Test.

Good to know: Agillic has no list to choose, so Scratcher starts sending as soon as you click Activate. Activate it before the campaign goes live, or set it up right away.

Field mapping

• The email address is always sent to the unique email field. You don't need to map it.
• The field list shows your Agillic person data, with its types. Dates are sent in Agillic's format, for example 31.12.2025.
• If you have a person data field for opt-in, map a consent's Accepted field to it.

What is sent and when

Scratcher looks up the recipient by email. If they don't exist, they are created; otherwise they are updated. New sign-ups are sent within a minute or two, and existing leads are sent when you activate it. Under Settings > Integrations > Delivery status you can see whether each lead was new or already existed in Agillic.

Troubleshooting

• "Agillic API request failed with status code ...": Agillic didn't accept the request. 401 or 403 means the key was deleted or lacks access; connect a new key.
• An Agillic message about a field: a value doesn't fit the field type, or a required field is missing. Check the mappings.