AFI AFI

Copernica

Estimated reading: 2 minutes Updated August 1, 2026

Copernica is a Dutch email-marketing and database platform popular with mid-market European brands. Advanced Form Integration sends form submissions to Copernica as new profiles in a chosen marketing database.

What you’ll need

  • An active Copernica account.
  • A Copernica Access Token with both SOAP and REST API access (Configuration → API Access Tokens).
  • The Advanced Form Integration plugin installed and activated.

Get your Copernica access token

  1. Log in to the Copernica Dashboard.
  2. Go to Configuration → API Access Tokens.
  3. Generate a token with both SOAP and REST API access enabled.
  4. Copy the access token.

Connect Copernica to AFI

  1. In WordPress, go to AFI → Settings.
  2. Enable Copernica and click Save Changes.
  3. Open the Copernica tab.
  4. Paste the Access Token and click Save Changes.

Create the integration

  1. Go to AFI → Add New.
  2. Configure the trigger.
  3. In Action → Platform, select Copernica.
  4. In Task, choose Add Profile.
  5. Pick the target Database: AFI fetches your databases automatically.
  6. Map the form fields to Copernica’s database columns. AFI loads the column schema for the chosen database, including custom fields. Select-type columns show their predefined options as a description during mapping.
  7. Optional: configure Conditional Logic.
  8. Click Save Integration.

Screenshot: AFI field-mapping screen with Copernica database and profile fields visible

Tasks supported

Add Profile

Creates a new profile in the chosen Copernica marketing database. If the database has uniqueness rules (typically on email), Copernica updates the existing profile rather than creating a duplicate.

Conditional logic example

Add the profile to your “Newsletter EN” database only when the form’s language field equals “EN”. Dutch subscribers go to the “Newsletter NL” database via a separate integration.

Troubleshooting

Integration doesn’t fire

Open AFI → Log and find the most recent entry. The log shows the request payload sent to Copernica and the response received, usually pointing straight at the cause.

“Insufficient permissions”

Copernica’s REST API requires a token with REST permissions specifically. If your token only has SOAP, regenerate it with both enabled.

Select-field rejected

Copernica select columns require values that match a predefined option. Check the option list on the database column’s settings. Case matters.

Related docs

Receiver Platforms - Previous CiviCRM Next - Receiver Platforms Emailchef