►First thought … CRLF (%0d%0a) is a Windows encoding. Did you try the unix encoding, LFLF (%0A%0A)?
►Second thought … Instead of URL Encoding CRLF or LFLF, what about URL Encoding the HTML Entity for new line, &NewLine?
►Third thought … Since I have set Spark as my default mailer, might using the mailto: URL scheme get around whatever the problem is with the Spark URL scheme?
I remember I had tried %0A, as well as <br>, and \n to get a single new lin. It looks like using mailto: is the key
Let me kindly note that we are not able to implement the outside created coding into Readdle apps.
That response feels like it might be an email template itself from a first line support person who didn’t understand what was being requested. I cannot believe it is not possible for them to decode a newline from a URL scheme given what they already have in place.
I wonder if mailto: would also be a way to get new lines into the body of Gmail.app? The internet is awash with posts of people asking how to do so with the Gmail URL scheme.
I responded by pointing out that Readdle supports URL schemes for PDF Expert and their calendar, so why not Spark. Maybe my response will kick the problem up to a higher level support person.
This new line issue with URL schemes is a pretty common problem with Mail clients. Most of them default to composing/sending HTML email these days, and don’t do the necessary conversions on their incoming text.
I think the Gmail app, Spark, Airmail, Outlook, and others have all either had or have this bug – and some have repeatedly fixed, and then broken it again over the years.
Even Apple screwed this up briefly last year in the Mail share extension. In the late versions of iOS 14.x, if you sent text to the Mail compose APIs or the mailto: URL it would pop up in the message with literal text Line1<BR>Line2<BR>!
Yes, during last night’s search for a solution, I stumbled upon this problem with Apple’s Mail.app for iOS.
I also read that mailto: is notoriously unreliable when it comes to including multiple email addresses in any of its recipient lists, i.e., to, cc, or bcc but I haven’t tried this yet.
So, mailto: may not really be the solution for my mailer need.
Thank you so much for your emails and provided information. Let me apologize for the misunderstanding.
I’ve just double-checked the information with our Quality Assurance team and would like to let you know the URL scheme, indeed, is available in Spark. However, the new line characters in the body text feature is not supported at the moment.
Please be assured that I’ve added your kind request to our Wish List for the developers to look through and keep in mind for further investigation of the matter. Once there is any update on the matter - I’ll be happy to let you know.
Also, if you have the Spark app set as your default mail client on your device, please consider using the mailto: link, as it will work the same way as the URL scheme.
Two years later - a little revisit. Choosing not to start all over again - because there might be some relevancy in here - suffice to say - long time user of Spark and a way longer user of Drafts. As a result been using Spark actions by both @agiletortoise and @FlohGro - not a massive user mind - just at times useful - thank you both.
A while back Spark released a new version of their product which changed a lot in how their mail worked and looked. I played around with it - and gave up - too much muscle memory.
Couple of weeks ago I tried again - and voila - off to the races.
Here’s the question … both actions I had no longer work - has Readdle changed their app so much that they broke the actions or is there something else going on? I have tried the old app - and the action doesn’t work there either.
Let’s start by checking out the basics. Based on the above discussiona, you should have Spark set as your default mail app and be using an action based on the mailto scheme.
If I copy, paste, and open the entry below in Safari, it opens a new, fully populated email in Spark.
thanks for saving me time This boy will continue to dream though - though I have to say there are some very odd decisions with ‘new’ spark, compared to ‘old’, like no ability to modify font type and size
What you could do is have a Drafts action that converts the content to rich text, then opens a mailto link, and you paste into the body.
There are usually other options if you just need to send a mail rather than going via Spark. Usually with mail automations you just want the mail to be sent, perhaps from a particular address. Sometimes you may want the opportunity to amend the mail, such as adding attachments prior to sending - but they need not necessarily be done with a default mail client.
Please note I am not against using Spark - I use it as my mobile device(s) email App; I use MailMate on my Mac. It just might not be the best choice for every instance of email automation.
I see that @sylumer has already replied in this thread and apparently debugged your problem with this Action, which seems related to Markdown.
I just want to add that I am very grateful to both @sylumer and @FlohGro for their help automating Spark. I use the former’s automation several times daily and it’s my sole use of Drafts.
removing all formatting - have to say is a GREAT benefit - though flip side is a fixed font - and size - even tho ‘old spark’ had that - but I do like that formatting tool bar.
! The 
The internet is awash with posts of people asking how to do so with the Gmail URL scheme.
This boy will continue to dream though - though I have to say there are some very odd decisions with ‘new’ spark, compared to ‘old’, like no ability to modify font type and size