With Transmit Code, you can setup a connection to any CRM or external marketing tool that supports a API.
It might seem hard to do, but it's really simple. Take a look at the examples below to add new subscribers to a MailChimp audience or ActiveCampaign list. Make sure you overwrite details like API-keys with those of your own.

• MailChimp
• ActiveCampaign

[TRANSMIT="https://us1.api.mailchimp.com/3.0/lists/1c15e4d9ab/members/"]
  {AUTH}
    user:1a20f1fa3243a3f4879a60c0a1082102-us1
  {/AUTH}
  {HEADERS}
    Content-Type: "application/json"
  {/HEADERS}
  {BODY}
    {
      "apikey": "1a20f1fa3243a3f4879a60c0a1082102-us1",
      "email_address": "{INPUT}",
      "status": "subscribed"
    }
  {/BODY}
[/TRANSMIT]

[TRANSMIT="https://proofly.api-us1.com/api/3/contacts"]
  {HEADERS}
    Api-Token: iljXqM4pOggPKq7PgNl8cudpwUscxm
    Content-Type: "application/json"
  {/HEADERS}
  {BODY}
    {
      "contact": {
        "email": "{INPUT}"
      }
    }
  {/BODY}
[/TRANSMIT]

Technical documentation

Transmit Code can be seen as a programming language, it was introduced and created by the Proofly team itself.
There are several blocks available to use, combining them results into a Transmit. Transmits are parsed on our servers to create HTTP POST requests to external tools. Each Transmit starts with [TRANSMIT] blocks. Inside, you define a destination (URL) for the data to get posted to. This must be an absolute URL starting http:// or https://.

It's very important that the same structure is kept like in the above example, otherwise, issues might occur. Watch the newlines!

Inside the transmit {BODY} you'll find the {INPUT} tag, this will be overwritten with the data that your Proofly notification has collected once the Transmit is being executed. This tag can be placed anywhere, as long as it is within the {BODY}.

You can create up to 5 transmits per notification by just combining transmits, so you can post data to MailChimp and ActiveCampaign in one code:

[TRANSMIT]
  ...
[/TRANSMIT]
[TRANSMIT]
  ...
[/TRANSMIT]

• {AUTH}

  Define HTTP authentication where the username and password is separated by a colon mark (:).
  Not required • Shouldn't contain more than 1 row.

• {HEADERS}

  Define HTTP headers, whose aren't required, but should be used when your body includes a special data format, like JSON.
  Not required • Can contain multiple rows. Each header should be added on a newline.

• {BODY}

  Defines the body/content of the request. Most external tools ask for a JSON-body.
  Required • Can contain plain text, JSON, XML or any other format defined by your external tool.