Hello, really enjoying Noloco so far. Used several other low code UI and workflow builders in the past month, and so far the UI for users/team is the best. Couple walls I’ve run up against that I’m looking for solutions for:
- Use Case: I have multiple suppliers each with multiple contacts associated. I am trying to create a communication UI that has email templates and a free-form field to quickly load commonly used emails. Eventually, I will send these using a workflow or 3rd party integration, but for now, just having a field that I can update from a template cell to the “Email Body” field in the UI with a copy to clipboard button is good enough. I can then use that email body field in a mailto: link. Here are a couple of my roadblocks:
a. The navigate to button action for Email doesn’t support multiple comma separated email addresses loaded via a lookup field, this is ok because I can use a URL field and manually create the mailto: with multiple emails addresses, cc, subject, and body.
b. The issue with the mailto: though is, my “Email Body” field has line breaks and when I pass “Email Body” to the URL button in the mailto:whatever@gmail.com?body={{Body Field}} the body field converts all spaces and line breaks to + instead of their URL formatted equivalent. There doesn’t seem to be a formula that will allow me to create a URL friendly string.
c. I want my email templates and users to be able to reference fields for the current record: {{companyName}}, {{geoTarget}}, etc. and have them replaced with the value for the current record. I can do this using SUBSTITUTE, but this gets really messy, really quickly, because you have to use nested substitutes and I have a lot of possible fields with new ones added frequently. It would be great to have a universal format that if I put {{fieldAPIname}} it will be replaced automatically with that value from that record. or {{Company.companyName}} to reference fields in Linked records, not as important because I can add lookup fields, but it sure would be nice 
I know markdown and HTML aren’t supported using the mailto: method, but basic URL encoding is. I’m hoping to eventually use the Email integration to pass markdown to Gmail to send emails, but that’s a little further down the line.
Any suggestions, workarounds, or creative ideas on how to tackle this use case?