Search the Community
Showing results for tags 'Email Plugin'.
Found 2 results
Need a Way to Send SMS/Text Messages from FileMaker? We have released a new update for the 360Works Email Plugin, version 3.1, allowing you to send text messages from FileMaker leveraging technology from Amazon Web Services along with improvements to the plugin when used on Windows. We like Amazon Web Services (AWS) and as you may have noticed, we use AWS technology in a lot of our product updates. AWS has been a scalable and reliable remote computing infrastructure for our software and we have a great depth of experience in implementing their services into our development. Recently, we've been working on improving the SMS/text message service for our Email Plugin, and Amazon's Simple Notification Service (SNS) API was the optimal technology to leverage for sending SMS in FileMaker. Unlike using other gateways, there is no need to hassle with lengthy account set ups and various expensive complicated pricing models. In fact, if you already have an AWS account you can get started for free and use the 360Works Email Plugin for sending text messages right now! How it Works With the 360Works Email Plugin now using the AWS SNS service, you can push out text messages to a large number of subscribers on their mobile devices. Example business use cases: Notifying a customer that a pet is ready for pick-up on their mobile device Sending project update alerts to teams on the go Confirming and reminding clients of appointment times via text message Virtually any case you can think of where a mobile message service is needed! The AWS functionality in the Email Plugin is easy to set up, operate, and reliably send notifications to all your endpoints - at any scale. It takes just 1 function call to send a text message from FileMaker; simply enter your AWS Access Key, AWS Secret Key, a phone number, and a brief message like so: EmailSMSSend("AccessKeyHere";"SecretKeyHere";"17702349293";"Your Message Here"] ...and you're done! Where required by local laws and regulations (such as the US and Canada), SMS recipients can use their devices to opt out. Developers can manage sending settings in their AWS console. Using the 360Works Email Plugin is a great way to send SMS in FileMaker Go. You can trigger a script on a machine that has the Email Plugin installed. Using FileMaker Server, you can have routine scripts that will process all the outstanding function calls or even use 360Works RemoteScripter Plugin to trigger server side scripts. Your users can send text messages from their FileMaker Go custom app, whether using an iPhone on the field or an iPad throughout the office. Pricing and Availability The Email Plugin is essentially a 2-for-1 deal. When you purchase it you receive the SMS/text message functionality as well as the powerful email sending capabilities of the plugin, such as sending and receiving HTML formatted and multiple attachment emails with SMTP, POP, and IMAP servers. The Email Plugin starts at $195 and is available with 3 different tiers: Single-User, Workgroup (10 users - local use), Enterprise, and Solution (Vertical Market option). If you plan to use the Email Plugin for server-side use of any kind, such as SMS in FileMaker Go, you will need the Enterprise license. This new version, Email Plugin 3.1, is a free update for those currently using major version 3. You can go right to the Email Plugin page and download the current version. Sending costs are extremely low and handled through AWS. The first 100 messages sent to US numbers are free. Messages after 100 sent and any non-US numbers incur a per message charge, pricing can be found in our docs wiki (docs.360works.com). Currently, this charge is less than a penny per SMS. If you would like implementation services, please contact us at email@example.com and we will be happy to take care of the entire SMS implementation process for you or provide a guided walk-through at our hourly consulting rate. It is free to try the Email Plugin. There is a fully-functional demo version available and you can test the functionality in our sample file as well. We value the feedback from the FileMaker Developer Community. Please let us know if there is a feature you would like to see in our plugin(s) at firstname.lastname@example.org "I wanted to publicly thank Sam Barnum from 360Works for OUTSTANDING customer support! I needed to be able to put inline graphics into outgoing "blast" emails for one of my clients. We use 360Works' email plug-in for it's ability to run from a script running in FMPS - these "blasts" go out to a few thousand people and run at night. Sam responded immediately to my request for help, offered to make an addition to the plug-in to handle the inline graphics and built it for me in very short order... So, THANK YOU SAM. And thank you 360Works." ?Mark Woytovich, Ignotum Inc. Free Demo or Download Email 3.1 Stay updated with 360Works
Our office recently replaced a database server and upgraded to FMS17 from FMS16. Now that FMS17 is being used, the Script Engine process terminates abnormally when 2 scheduled scripts using the Email plugin fire-off at the same time. Individually, the scripts run fine. However, run in tandem, they crash FMSE. Any thoughts on why the 360Works Email plugin would allow simultaneous scripts to run in FMS16 but not in FMS17? Server Version is: 126.96.36.199 Plugin Version is: 3.1 Sample Event Logs: 2019-03-21 17:35:00.166 -0600 Information 148 SERVERNAME Schedule "Email Example A" running. 2019-03-21 17:35:00.166 -0600 Information 689 SERVERNAME Schedule "Email Example A" has started FileMaker script "MyScriptA". 2019-03-21 17:35:00.166 -0600 Information 148 SERVERNAME Schedule "Email Example B" running. 2019-03-21 17:35:00.166 -0600 Information 689 SERVERNAME Schedule "Email Example B" has started FileMaker script "MyScriptB". 2019-03-21 17:35:11.371 -0600 Information 645 SERVERNAME Schedule "Email Example B" scripting error (1636) at "MyFile : MyScriptB : 26 : Send Mail". 2019-03-21 17:35:12.074 -0600 Error 701 SERVERNAME FileMaker Script Engine process has terminated abnormally. 2019-03-21 17:35:12.090 -0600 Error 757 SERVERNAME Schedule "Email Example B" aborted; FileMaker scripts can't be run because FileMaker Script Engine (FMSE) process is stopped. Use the command "fmsadmin start fmse" to start the FMSE process. 2019-03-21 17:35:12.090 -0600 Information 126 SERVERNAME Schedule "Email Example B" scheduled for 03/21/2019 05:45 PM. 2019-03-21 17:35:12.090 -0600 Error 757 SERVERNAME Schedule "Email Example A" aborted; FileMaker scripts can't be run because FileMaker Script Engine (FMSE) process is stopped. Use the command "fmsadmin start fmse" to start the FMSE process. 2019-03-21 17:35:12.090 -0600 Information 126 SERVERNAME Schedule "Email Example A" scheduled for 03/22/2019 05:35 PM. 2019-03-21 17:35:14.231 -0600 Warning 30 SERVERNAME Client "Email Example A (FileMaker Script)" no longer responding; connection closed. (10) 2019-03-21 17:35:25.452 -0600 Information 703 SERVERNAME Starting FileMaker Script Engine process...