Skip to content

Attio sequences always inject an unsubscribe footer; use composer sends for human-feel outreach

TL;DR.

Attio auto-appends a mandatory unsubscribe link to every email sent via Sequences (even single-step ones), which signals automation. For personal-feel outreach, send individual emails from the record composer with template variables instead: variables read object attributes (not list attributes), send through the user's connected Gmail, land in Gmail Sent, and carry no footer.

Building low-volume, personal-feel outreach (founder emailing creators) on Attio Pro:

  • Sequences force an unsubscribe link. Unsubscribe links are required and automatically included on ALL emails sent through Sequences — there is no toggle, even for one-email sequences (https://attio.com/help/reference/automations/sequences/email-deliverability-guide; community request to skip it for one-email sequences is unfulfilled). The footer immediately reveals the email as automated, defeating hand-written-style outreach.
  • The composer path has no footer. Regular emails composed in Attio (record page, c shortcut) send through the user's own connected Gmail account, appear in Gmail Sent, and support the same { template variables as sequences (https://attio.com/help/reference/email-calendar/send-emails-in-attio).
  • Variables read OBJECT attributes, not list attributes. If you sync per-contact personalization fields (demo URL, hook line, video title) from a pipeline, create them as custom attributes on the People object (POST /v2/objects/people/attributes — API-creatable on all plans), not as list attributes, or they won't be available as email variables.
  • No send/sequence API. Attio's REST API (see https://docs.attio.com/llms.txt) has no endpoint to send email or enroll in sequences; programmatic sending must go through Gmail's API directly, with Attio picking the thread up via its email sync.
No signals yet