Re:amaze combines email, social media, mobile, and chat conversations seamlessly so your customers can reach you however they want. Collaborate with teammates using assignments, notes, and shared views.
Below you'll find detailed information, specifically for Re:amaze integrations:
Supported Re:amaze Integrations
To authorize Re:amaze, we need your Subdomain, Email Address and API Token. These can be found as shown below.
If you already authorized Re:amaze account(s) in the past or in any other PieSync integration, you'll be able to skip the first part of the authorization and choose from your CONNECTED ACCOUNTS.
[IF] Supported Conditions/Filters
- Field values
- Already existing in the app you sync with
[THEN] Supported Actions
- Updating field values
Default Field Mapping
Depending on the other app you're syncing with, you'll see a number of standard Re:amaze fields being mapped by default. For instance, in a connection with Google Contacts, the default field mapping looks like this:
Customizable Field Mapping
You can custom map your Re:amaze Custom Fields and any additional standard fields that aren't included in the default mapping yet. Bear in mind a mapping between two fields can only exist if the types of fields are compatible, and the particular compatibility will determine the direction of the mapping as well. More information on Customizable Field Mapping here.
1. If the custom field already exists in your Re:amaze instance, make sure to enter the exact same name and format.
2. If the custom field does not exist yet, PieSync will add it for you, as a single text field.
Currently, there are no Re:amaze integrations on the PieSync platform that support our deletions sync.
Currently, there are no Re:amaze integrations on the PieSync platform that support our unsubscribes sync.