Uncanny Automator

Thanks @nurmansusanto , we really appreciate the review!

Hi @hypeonweb, thanks for the suggestion! That’s actually already on our roadmap. Keep an eye on our blog or sign up for our newsletter to be notified when it’s available!

In the meantime, if you have a very defined busy period each day, you can delay all actions by 12 hours, which would cause the actions to peak at the opposite time of your daily busy period.

Hi @polisson ,

Thanks so much for the review and feedback! We’ll see what we can do. ??

Hi @polisson, if you have a few minutes, we’d love it if you could leave us a review:
https://www.ads-software.com/support/plugin/uncanny-automator/reviews/?filter=5#new-post
Our team would appreciate it a lot!

Great! Glad that resolved the issue. We’ve responded to your LinkedIn question as well.

Thanks!

Hi Paul, unfortunately, the current LinkedIn action cannot include an image with the LinkedIn post.

We’re planning to add a new action “Publish a post with an image to a LinkedIn page”. This is similar to the Facebook action “Publish a post with an image to a Facebook page”.

It’s a bit complex working with the LinkedIn API for post images as it requires multiple calls – one to upload the image and another to add the image to the post.

Keep an eye on our blog; we’ll make an announcement when it’s available. Thanks for your patience!

Hi Paul, can you confirm what you mean by “I’ve got posts saying I posted on facebook and instagram”? If you mean that you’re seeing extra content posted to facebook and instagram that you’re not expecting, check that you’ve specified a post type in your trigger (you probably want “Post” if you’re trying to send blog posts to social networks), not “All post types” as that will usually generate unnecessary content.

If that’s not the issue, can you share a screenshot of your recipe and the unwanted output on social media? Please redact any sensitive info.

Thanks!

Sorry for the delay and thanks for the suggestion! I’ve added your request for those line items to our development queue. If it’s feasible, we’ll get them added to an upcoming release.

Thanks!

Sorry for the delayed reply! That does seem like an oversight; I’ve added that token to to our development queue and you should see it in an upcoming release.

In the meantime, you should be able to get the product price by using the Post meta token. Enter the Product ID token and use the meta key _regular_price or _sale_price to retrieve the price you want.

Hope that helps!

Hi @rikprogeek ,

Thanks so much for taking the time to write a review! We really appreciate the kind words.

Hi @bottas Thanks for providing an update with the solution! We’ll update the field description to make it clear which formats will work.

Thanks!

Hi @bottas, thanks for the screenshots!

Everything looks fine there, so I think we’ll need to do a little bit more investigation.

Can you use this form to send us a link to a blog post that was successfully posted to Twitter as well as a link to a blog post that failed to be posted to Twitter so we can take a look at the posts and see if we can spot anything that might have caused the problem?

Thanks!

Hi @bottas , sorry to hear about the issue! I’m sure we can figure out what’s causing it.

First, it would really help to see screenshots of the edit recipe page where it sometimes fails so that we have more context.

What we would also suggest is adding a new “Send an email” action to the recipe for testing purposes. In the action, send yourself an email that outputs all of the tokens that you’re using in the recipe.

When a recipe fails with the URL error, check the email to see what URL is being passed to Twitter. Is it valid? Can you send us an example of one that was rejected?

Thanks!

Yeah, agreed, “Logged In” is a bit misleading, but we needed something short and simple to try to capture “Recipes involving WordPress user account data or user activity in some way when they’re initiated”. That recipe type doesn’t mean a user is actually logged in when they run or to run them, just that they always involve WP accounts in some way (vs. something like a form submission that can be trigged by a visitor with no WordPress account and never involving a WordPress account). We try to explain this a bit in the recipe selection screen, but on our integration pages it lacks that context–and can be confusing.

We have some ideas about how to address this in a future release with a pretty big overhaul, but that initiative is probably ~6 months away.

Thanks for the feedback!

It’s because we consider them WordPress functions.

Have a look at https://automatorplugin.com/integration/wordpress-core/. That’s where you’ll see triggers like logging in, a user being created, etc. Certainly we wouldn’t miss basics like those!