I have a template named "Basic" that has two versions, different from each other - a draft one and the published one. Is there a way - through Mandrill API - to send the draft version, not the published one - or just in general to choose which version of the two to send?
If you haven't published the template before, when you use the send-template api call, the draft version should be sent. The draft vs. published option is generally to allow editing an already-published template in the application without affecting what's being sent via the API. If you have already published the template, and also have a draft, then in the web interface in the test menu is an option to send a test, which should allow you to send a test of the draft version instead of the published version.
Related
We'd like to allow our users to make changes to our ERP (only very limited conditions) from within the smartsheet. Is there a way to add a web service call based on changes to a cell?
It's certainly possible to do what you've described (provided, of course, that your ERP supports inbound web service calls to update data there).
If you're wanting to do this programmatically (i.e., by writing a script in Python or any other supported language), you can use the Smartsheet API to create one or more webhooks that will monitor Smartsheet for the type of changes you specify, and send your integration notifications when those events occur. Your integration would then listen for those inbound event notifications, and when they are received, it would programmatically issue the appropriate web service call(s) to update data in the ERP.
It's also worth mentioning that, depending on what ERP you're using, it may be possible for you to accomplish your goal without having to write any code. If you're interested in exploring the feasibility of that approach, I'd suggest you check out products like Zapier, Power Automate, etc. to see if they offer a connector for Smartsheet and your ERP. You may also want to check out the Smartsheet Connectors and Integrations page to see if there's a connector for your ERP listed there.
I'm exploring the possibility of building a centrally hosted email client, embedded within my site. Users would be provisioned a new email address from me, they are not using their existing email. Essentially, I'm looking for the feature set of an email web client (multiple user accounts, get inbox messages, read, delete, compose new, organize, etc) exposed as set of RESTful APIs. A brief web search uncovered very little meeting my desires, but I did come across http://jmap.io. I was unable to find an existing implementation of the specification that I could leverage for my solution, and would love to avoid writing my own. Are there any existing solutions (JMAP or otherwise) that might meet my needs? I've ruled out https://context.io/ because I cannot have the emails stored or consumed by a third party.
I'm actively contributing to the Apache James Server. As part of my work, I am working on a JMAP implementation with my co-workers.
So far, we are able to build a working web-mail on top of it in one of our company product, OpenPaas.
And as it is an Apache project, it is OpenSource. Maybe you want to have a look...
https://github.com/apache/james-project/tree/master/server/protocols/jmap
http://james.apache.org/
I just want to add that as for now (2020) Cyrus IMAP also has JMAP support.
Stalwart JMAP server was just released (September 2022) and it includes full support for JMAP Core, JMAP Mail and JMAP over WebSocket. Support for JMAP Contacts and Calendar will be added as soon as these become IETF standards.
Does the API Manager / Bluemix provide an interface (API, hook) to automatically update API definitions when I push Swagger 2.0 API definition changes to a GitHub repository?
This is currently not possible. Your best bet is to manually re-import the Swagger using the GitHub raw URL every time you update it; however, doing this will require that you create a new API via the import, remove the old API, and then add the new to the same plan and re-deploy.
You can manually update by clicking the Update button in the API editor. It looks like this:
Using this feature will automatically overwrite all changes you've manually made to the API, so it's recommended that you create a new API revision before uploading an updated Swagger doc.
If you plan to make manual changes to your API via the API Manager UI, then you may be better off making small updates by hand.
If you really need an automated approach, you may be able to write your own app / script that gets called any time the Swagger is updated in GitHub, and then can call the API Manager APIs to update the Swagger. This will likely be pretty complicated to set up.
We are currently using Freshdesk for our customer support and GitHub for our code. On receiving a bug or an improvement feature request via Freshdesk, we would like to forward that ticket (with all the details + screenshots) to an email in GitHub so an issue is created automatically on GitHub. That would save us a manual entry.
Look forward to an advice on this or a better solution.
NOTE: Had come across https://zapier.com/zapbook/gmail/github/72/create-github-issue-email , but we would prefer a direct interaction without a third-party app in between.
Creating an issue to GitHub wouldn't be done by "sending an email", but only by using the GitHub v3 issue API (like this script, for example, to migrate issues to GitHub)
That means in your case having a trigger on FreshDesk (or an "Observer" to call a webhook) which would parse the ticket and create the appropriate bug report on GitHub.
From the Observer/WebHook help page:
Webhooks also come handy when you want to trigger an action in an external application or tool (as well as some updates that the Observer can't perform, like update time entry on a ticket or add a note to a ticket)
You would manage that webhook locally on your side, and that callback would in turn call the right GitHub API commands to create the GitHub issue.
We had similar needs and built a very simple tool to let anyone in the team send/forward emails to create GitHub issues. We were using it internally at first so that non engineering team members didn't have to go to GitHub to create issues. We just made it available to anyone (and free). It supports attachments.
You can find it at https://fire.fundersclub.com.
i want to create a RemoteScheme , with set new mail notifications , then update jira project with new mail notifications i created use jira soap api.
can any one give some ideas?
thinks!
Your easiest way is to create a new JIRA plugin that provides a new SOAP endpoint. Usually less than a day's work but since it involves notification schemes it's probably a couple of days to get right. This all assumes you're comfortable writing JIRA plugins and writing Java.