What you get
The integration runs in both directions, and each direction works on its own. You can turn on one without the other.
Attio reads Bloom
A Bloom engagement widget on people records shows how a contact has engaged with your emails, and opens a full timeline when you click it. An Email engaged workflow trigger starts a workflow run every time a recipient opens or clicks one of your tracked emails.
Bloom writes to Attio
Every contact who engages is pushed into your workspace as a Tracked Emails record linked to the matching person, refreshed about a minute after each open or click. This part is switched on from Bloom, not from Attio.
Before you start
- The Bloom extension for Chrome, added from the Chrome Web Store. It is the part that tracks your Gmail sends, so nothing reaches Attio without it. Tracking happens as you send, which means an email sent before Bloom was installed has no engagement to show, here or anywhere else.
- A Bloom account and workspace on app.bloomtag.io. Signing in from the extension creates the account, and the dashboard then asks you to name a workspace. Nothing is tracked until that workspace exists, so this step is not optional. The dashboard is also where the sync into Attio is switched on.
- An Attio workspace where you are allowed to install apps.
- For the workflow trigger, an Attio plan that includes workflows. A new workspace starts on a trial that does.
One Bloom workspace pairs with one Attio workspace. Connecting the app from a second Attio workspace replaces the first connection, and the widget in the first workspace stops returning data.
Install and connect
Install the app. Open Bloom from the Attio App Store and choose the workspace to install it into.
Connect it to Bloom. Attio opens the app page and asks for a connection. Press Connect. You land on app.bloomtag.io, where you sign in if you are not already, and the consent screen names the Bloom workspace you are about to connect. Press Allow access. Attio stores the credential itself; there is nothing to copy or paste.
Add the widget to your people layout. Open any person record, then the ⋮ menu at the top right, Configure page, + Add widget, and pick Bloom engagement under Apps. Save your changes. You do this once per layout, not once per record.
Turn on the sync into Attio. In Bloom, go to Settings, find the Attio card and run Step 1 · Connect Attio. The card then reports the health of the sync, and Step 2 confirms the app is connected.
Attio's Highlights section holds six widgets and the default layout is already full. If Bloom engagement will not go in, remove one first: hover a widget, open its ⋮ menu, and choose Remove widget.
The engagement widget
On a person record, the card reads the contact's first email address and shows the engagement Bloom has recorded for it: the number of opens and clicks, when the last activity happened, and a badge that reads sent, opened or clicked.
Click the card to open the full timeline. It lists every tracked email sent to that contact, newest first, and every open and click inside it. Automated opens are not hidden, they are labelled as bots, so a burst of opens from a security scanner is visible for what it is rather than silently inflating the count.
The counts on the card exclude bots and exclude your own views of your own email. They are the same numbers Bloom shows you in Gmail.
The workflow trigger
Email engaged fires a workflow run every time a recipient opens or clicks one of your tracked emails. It has no configuration: it fires on every human engagement in the workspace, and you filter downstream on the values it exposes.
In Attio, go to Automations → Workflows → New workflow → Start from scratch.
Search for engaged and pick Email engaged, under Bloom.
Add whatever should happen next: create a task, post to Slack, update a record.
Press Publish changes. Bloom starts sending engagement to this workflow at publication, not before, so an unpublished workflow never fires.
Each run receives these values:
| Variable | What it holds |
|---|---|
recipient_email | The address the tracked email was sent to. |
event_type | open or click, the event that fired this run. |
status | Where that email stands overall: sent, opened or clicked. |
subject | The subject line of the tracked email. |
occurred_at | When the open or click happened, ISO 8601 in UTC. |
tracking_id | Bloom's stable identifier for that email. The same value keys the Bloom Emails record, so a workflow can match one to the other. |
Only human engagement fires the trigger. Opens Bloom attributes to a bot, and your own views of your own email, never reach your workflows.
What Bloom writes
Once the sync is on, Bloom creates a custom object called Tracked Emails in your workspace and upserts one record per tracked email, keyed by its tracking id and linked to the person it was sent to. Each record carries the subject, when it was sent, the current status, the open and click counts, and when the last open and click happened.
Because every write is an upsert on a stable key, the same email is corrected in place as engagement accumulates rather than piling up duplicates.
If your Attio plan's custom object quota is already full, Bloom falls back to writing the same aggregates as bloom_* attributes on the person record instead. That choice is made once per workspace and does not flip back on its own if you later upgrade.
Opening a person record writes nothing. The widget only reads, and the sync is the only thing that writes.
Data and permissions
- The widget sends one contact's email address to Bloom and receives that contact's engagement. Nothing else leaves your workspace when you open a record.
- The trigger receives one call from Bloom per human open or click, carrying the fields listed above.
- Bloom never logs the contact's address or the workspace credential. Failures are logged as a status code and nothing more.
- The credential is issued to your Attio workspace and stored by Attio. It is only ever read server-side, never by the widget in your browser.
- What Bloom stores and why is set out in the privacy policy, and the terms of service cover the rest.
Troubleshooting
The widget always tells you what it is waiting on rather than failing silently. Each message below is what you will actually read on the card.
The app is installed but has no connection yet. Open the Bloom app in Attio and press Connect, step 2 above.
The credential is no longer valid. This happens after a Disconnect in Bloom, or when the app was connected from a second Attio workspace, which replaces the first connection. Press Connect again.
Bloom could not be reached. Nothing is lost and nothing needs doing; reopen the record in a moment.
Bloom is connected and has nothing to report for this contact. Either no tracked email has been sent to them, or the emails predate your Bloom install, or the only opens so far were automated ones, which Bloom does not count.
The person record has no email address, so there is nothing to match engagement against.
The workflow never runs
Check that the workflow is published: Bloom is told about it at publication, so a draft never fires. Check too that your plan includes workflows. If the workflow was deleted and recreated, publish it again so Bloom picks up the new one.
Records are not appearing in Attio
The sync is a separate switch from the app. Open Settings in Bloom: the Attio card reports whether the sync is healthy and, if it is not, what is failing.
Removing Bloom
Press Disconnect on the Attio card in Bloom's settings. That revokes every credential the app holds for your workspace, drops the queued writes instead of retrying them, and stops the sync. Then uninstall the app from Attio if you also want the widget and the trigger gone.
Records Bloom already wrote stay in your workspace. They are yours; nothing is deleted on the way out.
If you disconnect and later change your mind, both halves have to be redone: press Connect again in Attio, and run Step 1 · Connect Attio again in Bloom.
Support
Write to hello@bloomtag.io. Telling us the Attio workspace and roughly when the problem showed up is usually enough for us to find it.