How to set up Inbound Emailing with Postmark’s Inbound Processing

[paritosh.mehta19]

That’s great to know that you managed to figure this out James.

I had noticed that, but never anticipated that the test initialization could send a different request v/s an actual email. This makes sense now. Thanks for posting the fix on the forum.

[ryanck]

Hey @maru

Awesome post! Can you explain how you do this?

You create a random string in the user’s data table as a field called “reply_to” with the @yourappdomain.com and store the “asdf1234qwer_iopu7890hjkl@yourappdomain.com” or something like that?

@maru

C) To make sure incoming emails are routed to the right user, conversation, whatever you want to use the data for, you should assign individual keys to each user, message stream, etc. in your app and set them as the reply_to address when you send outbound emails for conversational transactional emails.
We solved by setting outbound email reply_to email addresses as INDIVIDUALKEYUSER12DIGITS_INDIVIDUALKEYANOTHERTHING12DIGITS @yourappdomain.com (e.g. asdf1234qwer_iopu7890hjkl@yourappdomain.com).
When a user replies to an email, the app will cut the reply_to information from the Postmark call using find&replace and truncated_to and do a search for the right user and message stream.

Thank you so much in advance.

[coty]

What you need to do to detect / process requests after the intial “detect data” is simply to remove /initialize in url.

You can then select “check” without having the detect data box open on bubble and should get a http 200 response.

[wordpresschef]

Hi everyone,

first of all thank you all for this precious information.

I’m struggling with this part of the process:

I’m able to parse the inbound email ( a reply to a task’s comment notification email) and I got this information from the JSON parsed data:

https://capture.dropbox.com/huUzGL4MgGGVMmj4

where I stored the user unique ID and the “task” identification ID

but I don’t get ho to retrieve them inside my “create new thing” action:

https://capture.dropbox.com/5920Lc6rZmOXJJkW

any help would be really appreciated.

[ericwuu]

I have been waiting on this pop up for hours…

[maru]

Have you pasted and saved the URL in postmark? A test request should be sent. You should be able to also receive something on the webhook if you send an email to your postmark inbound email address.

[fleuri.adon]

Hey,
I tried your process to download the attachments but I can’t access the data on this one.
Here is the JSON I have from the webhook

 "Attachments": [
    {
      "ContentLength": 541319,
      "Name": "passeport_fleuri_compressed.pdf",
      "ContentType": "application/pdf",
      "ContentID": "f_lggfksnb0"
    }
  ]

I think that Postmark has changed some parameters in their API because I can’t see the data in base64…Do you guys have an idea on what’s going on ?
Thanks

[fleuri.adon]

I fixed the issue by myself.
FYI, you need to send a request to your workflow from Postman using the following json at this page: Parse an email | Postmark Developer Documentation.
Happy no coding

[K.T]

Can confirm, you still need this workaround from James as of the time of this reply. Postmark still hasn’t resolved it.

[brad.h]

has anyone been able to set a friendly reply to address? like support@domain instead of [LongUniqueID]@domain.

@maru

We solved by setting outbound email reply_to email addresses as INDIVIDUALKEYUSER12DIGITS_INDIVIDUALKEYANOTHERTHING12DIGITS @yourappdomain.c

The person replying actually sees this XXXXXXXXXXX@yourappdomain when they reply. It’s possible to have everyone reply to a friendly email like support@yourappdomain and instead use the In-Reply-to Header to pass the unique ID. That way the unique ID is hidden and the expereince is better.

Example:

All replies to bubble support are to are to support@bubble but they’re able to keep things orgnized.

The In-Reply-To header and the Reply-To header serve different purposes:

• Reply-To Header: This is the email address that your email client will use when you hit “reply” to an email. In the Bubble email example the Reply-To header is set to:

Reply-To: support@bubble.io

This means that when you reply to the email, your reply will be sent to support@bubble.io.

• In-Reply-To Header: This header is used to track the relationship between emails in a conversation. It contains the Message-ID of the email to which this one is replying. For example:

In-Reply-To: <2344sdef3rr45f4f3rf332984@frontapp.com>

You can see bubble uses frontapp for support tickets. I just dont know how to accomplish this in postmark. has anyone done this?

[net-tt]

I assuem you have solved this problem. Postmark supports plus addressing since the original post. So now you can do support+clientid@myapp.com.