Connect BulkData.ai to the tools you already use

You can run any sync on demand at any time, and a signal can trigger one the moment it fires. Scheduled syncs are intended to run hourly on paid plans and once a day on the free plan — the exact cadence per plan is still being finalised, so check the schedule shown on the connection itself rather than assuming a number.

Yes. During setup you match each BulkData.ai field to a field in the destination, including custom fields, as long as the destination exposes them through its API. The mapping is saved with the connection and reused on every later sync, so you only do it once.

Moving a record you have already revealed costs nothing extra — the credit was spent at reveal. A sync that reveals new contacts, or re-enriches records whose data has gone stale, spends credits at the same rate as any other reveal.

The narrowest scope that still does the job: read access to the objects and fields you map so records can be matched, and write access to the objects you pick as a destination. Integrations do not request access to your email, calendar or files. The full scope list is shown on the provider’s consent screen before you approve anything.

Each connection has a matching key — usually work email address, falling back to the destination’s own record ID where one already exists. A record that matches something already in the destination is updated in place rather than created again, and you choose per field whether BulkData.ai overwrites the existing value or only fills a blank one.

Not today. The flow is one-way: BulkData.ai writes into the destination and reads only what it needs to match existing records. Two-way sync, where edits in your CRM flow back into BulkData.ai, is on the roadmap and has no committed date.