when using DocuSign SOAP API to create envelope and assign a valid email address to BCCEmailAddresses value in the create envelope from template API request boy. However, that email never receive any email during testing.
The DocuSign SOAP API guide mentions "BCCEmailAddresses – Only users with canManageAccount setting can use this option.". How to configure that from the latest Demo DocuSign site?
Is there way to configure DocuSign site account to BCC every DocuSign envelopes sent to recipients(during SENT event) rather than indicating it in every SOAP Create Envelope API request body?
I'm not aware of a feature that automatically add a BCC recipient for every envelope on the account. It's possible an old feature like that existed a long time ago, but it has been deprecated.
The alternatives:
Use DocuSign Agreement Actions. That capability of taking an action when an envelope was signed to archive it or send it to somewhere.
Use a third party API automation tool (like Microsoft PowerAutomate) and add a flow that does this.
Use webhook and build a simple integration using DocuSign Connect that sends the email with the completed document to the addresses you specify.
Related
I have a domain which uses Google Apps for Business to handle email. I already have it mostly set up--MX records point to the correct location and my domain is verified.
I'm now writing a python app (with Django) that will need to serve mail from my domain. What's the correct way to do this with Google? Should I create a Google Apps "user" for the organization as a whole, and then authenticate via SMTP as that user and send mail from there?
The Gmail API says that it
is the best choice for authorized access to a user's Gmail data.
and that
Automated or programmatic message sending
is a typical use case. However, I'm not trying to access a user's data or send mail on behalf of a user, but on behalf of my domain. What's the correct way to proceed?
Any help much appreciated!
You could use SMTP or the Gmail API based on your description. In both cases, you'll need some sort of service account to send mail from. With SMTP, as you mentioned, you'll be authorizing via the instructions you linked.
If you choose to use the Gmail API route, you'll be authorizing the API usage with the account. The Gmail API has many other use cases (e.g. to access user's data) but you're only using it to send emails on behalf of a service account you control.
I am developing an application, where I have a use case where I advertise a particular email id on a web site. Now, I need people to send me some information and an attachment to that email id . When I receive that email, it should trigger some action in my web application, such that I have both this document and the body of the email available to be in my web application. Then I can parse this information and take appropriate action. Let me know if it is possible to do this kind of email processing using Mandrill or Mailgun or SendGrid, and if yes, can you provide details/documention links on how this can be done.
Thanks
kabir
All three of those services support "inbound" email parsing, which should allow you to process and react to received emails.
Essentially they'll receive and process the email on your behalf, and send you a webhook with normalized data. Docs links below.
SendGrid Inbound Parse Webhooks
Mailgun Inbound Routes API
Mandrill Inbound Email Parsing
I see in the SurveyMonkey API there is the send_Flow call, that allows you to create an email collector and an email for it. Is there a way through the API to send a reminder email for an existing email collector? If not, does SurveyMonkey have any plans to add that functionality to the API in the future?
There is currently no way to send a reminder through the API. send_flow doesn't even send an email from the API; it just sets it up and requires a user to complete sending the email from SurveyMonkey's user interface (that's why it's a "flow").
It's possible that the ability to send reminders will be added to the API after sending programmatically is possible, but it's impossible to make and guarantees on future functionality or timing of API features.
I am trying to figure out how can I make it possible to send an email from my
application to Sendgrid and have it come back.
I want to use coldfusion to send an email using X-SMTP API. I found a documentation
online here but still wondering if there's any documentation available other
than the web API one?
http://thehatrack.net/blog/integrating-sendgrid-with-your-coldfusion-application/
SendGrid's Event Webhook is the only way to get email reads on an individual basis. This will POST an event to your server every time an email is read (among several other events).
The only "pull" based solution to get individual email events from SendGrid is the bounces endpoint, which will tell you when an email bounces (and is certainly not read), but nothing else.
If you want to retrieve individual read events from SendGrid, you'll need to connect the Event Webhook to an external service like Keen.io, and then leveraging their API to get individual events.
In our SaaS application each company (tenant) is given their custom domain like companyName.ourapp.com
We would like to provide some email services like:
Ability to send and receive email notifications from info#companyName.ourapp.com and similar addresses
Ability to create new email accounts in clients' subdamains at runtime, programmatically, when needed. For example we would have separate emails created for each "opening" so that emails sent to this address would be parsed info would be extracted
Similar tasks
For now I just don't even know on where to look and how this could possibly work.
As far as I understand email it should be some kind of custom mail server (SMTP) serving all sub-domains and having API we can use to send emails, list and retrieve messages etc.
Please suggest how it may work and is there any components out there we can use to implement this.
There are three options for this.
Create an email server and programatically configure it to accept or deny the specific accounts. Then use cron to poll via pop3 or imap and download the messages for the account. You can then send them on for the customer or handle them in your web app.
Create a script that is fired by the email server as it receives each email. The script can then handle what to do with the email as it's received.
Use a third party to receive the email via HTTP Post at your app. Using CloudMailin for example would allow you to create a custom authorization filter that would call your app in realtime and determine if the given account exists and messages should be accepted for it.
I wrote a blog post for Rails about receiving incoming email, however the principals would apply to any programming language and framework.