Hey 👋 Working through the Reply API for a 100+ sequence client buildout. One gap I can’t crack: ✅ Working: PDF on a step at creation time via POST /v2/campaigns with steps[].templates[].emailTemplateId (template has attachmentIds set). UI shows it, sends deliver with the PDF attached. ❌ What I need but can’t find: a way to add a PDF to a step in a sequence that already exists. Things I’ve already tested and confirmed don’t work: • PATCH /v2/campaigns/{id}/steps/{stepId} with attachmentsIds: [id] — accepted, silently persists [] • PATCH setting emailTemplateId post-creation — pulls subject + body from the template, but not the attachment • All v3 step variant attachment fields (attachmentIds, attachments, fileIds, templateAttachmentIds) — silently dropped • save-as-template → create-from-template — strips attachments on clone • Every plausible hidden endpoint I could think of (/v3/sequences/{id}/steps/{step_id}/attachments and variants) — 404 Has anyone found a working API path — documented, undocumented, or via a workflow tool — to attach a file to a step in an already-created sequence? Or is rebuild-from-scratch the only option today? Cheers 🙏

Hey, Hessan! Thanks for flagging this, and for the depth you've already put into testing. You've clearly looked harder than most people would before asking, so this isn't user error. Let me get with our team and come back to you here with a possible solution. Give us some time to look into it.

Hi @Dasha, indeed i exhausted all test/trial paths via Claude 😞

Hello @Hessan Haiderzada, thanks for highlighting this gap. This piece of functionality is not covered indeed. It will be shipped in the next release.

@Borys Boiko can you please give me release date? rough ETA?

@Hessan Haiderzada Planned on May 14th

@Borys Boiko Hiya, are you still on track with May 14th

Hey @Hessan Haiderzada, quick update here. The team is still actively working through the implementation details for this functionality. The original ETA was a bit too aggressive on our side, so at this point it’s more likely landing sometime next month rather than this week. We’d rather avoid overpromising dates while the work is still in progress. Appreciate you surfacing the use case though, it’s a legit gap, and the detailed testing you shared was genuinely helpful for the team.

@Dasha Dasha — given the 4-week timeline and the fact that I have 51 live sequences needing PDF attachments before then, can Reply grant Aexus written authorization to use the internal UI endpoint for step-level attachment binding, scoped to my account and time-boxed until the v3 endpoint ships? Specifically: I'd be calling the same endpoint the UI calls when I attach a file to a step. I can identify it via DevTools network capture and share back with your team for confirmation before running anything. Volume would be ~150 attachments across 51 sequences, run during off-hours so it doesn't load your infrastructure during peak. Happy to put this in a short email to whoever on your side needs to approve, with the specific endpoint and request shape documented. Goal is to not work around your team — I just need to bridge the next 4 weeks.

Hey Hessan! really appreciate how thoroughly you laid this out 🙏 the off-hours run + DevTools capture + endpoint docs is exactly the right way to approach it. good news though: team just confirmed this is already fixed on our side, so you shouldn't need the workaround. could you give step-level attachment binding another try and let me know if it's working for your use case? thanks again for flagging it so clearly 🚀

@Dasha Confirmed working ✅ Tested the new flow end-to-end on a dummy sequence: POST /v3/attachments → PUT /v3/sequences/{id}/steps/{step_id}/variants/{variant_id} with attachmentIds. Variant flipped to hasAttachments:true and the live send-test arrived in my inbox with the PDF attached.