Question 1

What Reply data can Polytomic sync?

Accepted Answer

For reads: contacts, accounts, contact lists, account lists, custom field definitions, sequences, tasks, email accounts, and email templates. Two things are absent and worth knowing. There is no separate campaigns object, and there is no statistics or reporting object, so aggregate campaign metrics are not synced. Sequences expose basic metadata and status only. Contacts do carry their current sequence, step, account, and enrollment status, which covers most reporting needs without an aggregate object.

Question 2

What can Polytomic write into Reply?

Accepted Answer

Contacts only, using update or create. Existing contacts are patched and new ones are created, and you can write custom field values through the custom field mapping with per field control over create versus update behavior. Identity is either the Reply contact ID or an email address. Accounts, sequences, lists, tasks, email accounts, and templates are all read only, and there is no delete or remove mode.

Question 3

Can I add or remove prospects from sequences from my data warehouse?

Accepted Answer

No, and this is the main limitation to plan around. Adding a contact to a sequence, removing them, and pausing or resuming their enrollment are not supported, nor is pausing or modifying a sequence itself. Sequence membership is read only through the contact record. So the workflow this connector supports is keeping contact data and custom fields accurate in Reply, with enrollment decisions still made in Reply. If enrollment automation is the requirement, that is worth raising with us.

Question 4

Does Reply sync incrementally?

Accepted Answer

No. Every execution pages through the full object using offset pagination at around a thousand records per page. There is no last modified checkpoint, change feed, or deletion detection, even though contacts do expose modification timestamps. Combined with Reply's monthly API call allowance, that means schedule choice matters more here than with most connectors. Daily is comfortable for typical contact volumes; running an ETL sync continuously against a large contact database is not the right pattern.

Question 5

Why sync data warehouse data into Reply?

Accepted Answer

Because outbound targeting is only as good as the data behind it, and that data rarely lives in the sequencing tool. Which accounts are already customers, which have open opportunities, which showed product intent, and which asked not to be contacted are all computed in your data warehouse. Reverse ETL keeps contacts and their custom fields aligned with that, so reps personalize on current information rather than whatever was loaded when the list was built. Running ETL in the other direction closes the loop by letting you attribute pipeline back to outbound activity.

Reply

Perfect pairings

Read and write contacts

Broad read coverage

Custom field support

Example workflows

What you can sync

From Reply

To Reply

How it works

How to set up

Frequently asked questions

Why teams choose Polytomic

No engineering required

Flexible data modeling

Handles scale automatically

Start syncing your data with Reply in minutes

More integrations beyond Reply