iBluSend

iBluSend brings business iMessage into Attio so your team can reach people from the records where relationship context already lives. Open a focused composer on any Attio people record, choose an eligible iBluSend line, and dispatch a one-to-one message without switching tools. Add the Send with iBluSend step to a workflow to send the same kind of message automatically. Your Apple credentials remain on your connected iBluSend hardware, while Attio receives a clear activity note after iBluSend accepts the request.

The app has two surfaces.

People record action

Open an Attio people record and choose Send iMessage with iBluSend from Quick Actions. The app reads that record's phone fields, requires an unambiguous E.164 number, and preselects the single online, available line marked primary in the connected iBluSend workspace. An operator can choose another eligible line for that dispatch. iBluSend then returns an honest accepted or dispatched result, and the app adds an activity note to the person record. Missing phone numbers, unavailable lines, ambiguous workspace configuration, expired connections, and API errors all fail closed before a dispatch is attempted.

Workflow step

Add Send with iBluSend as a step in any Attio workflow. The step has three fields.

• Recipient. The phone number iBluSend sends to. Pick a phone attribute from the triggering record, use a variable from an earlier step, or type a number in international format. The step does not read a record on its own; it sends to exactly the number in this field.
• Message. The text to send, 1 to 5,000 characters. Workflow variables are supported.
• Log on person record. Optional. When set, the step adds the same activity note the record action adds to that person record after iBluSend accepts the message. When empty, the step sends without writing a note.

The step always sends from the one online line marked primary in the connected iBluSend workspace. There is no per-step line choice. If no primary line exists, more than one is marked primary, the primary is offline, or its daily availability is used up, the step stops on the Line unavailable outcome without sending.

The step returns one of six outcomes: Accepted (with the iBluSend message ID, the line used, the accepted or dispatched status, and whether the note was written), Invalid recipient, Line unavailable, Recipient opted out, Plan access blocked, or Failed. A retried run of the same workflow execution reuses the same idempotency key, so iBluSend sends at most one message for it.

Install iBluSend and connect your iBluSend account through OAuth. On the consent screen, explicitly choose the iBluSend workspace Attio should use; the connection requests only lines:read and messages:send. In that iBluSend workspace, make exactly one online line primary and confirm it has remaining availability. In Attio, the app uses Records: Read, Object Configuration: Read, and Notes: Read-write. Then open a people record and launch the iBluSend Quick Action, or add the Send with iBluSend step to a workflow. An eligible iBluSend plan, connected line, and valid recipient are required for live dispatches.