Uncanny Automator

Hi @tennisgator , thanks so much for the review and kind words!

Hi Ivan,

Thank you for providing such a detailed message. It seems there are two separate issues, so I’ll address them individually below.

Issue 1: uap_options Table Notices

The uap_options table should be generated automatically, and any related notices should resolve on their own. However, if they persist, I’ve included additional steps below to help address the issue.

Issue 2: Hardcoded wp_ Prefix

We did find a hardcoded wp_ prefix in one of the plugin files, but interestingly, that file hasn’t been modified for months. It’s a bit unusual that this issue surfaced now, given it hasn’t been reported before. To help us investigate further, could you please provide the System Status Report? You can find it by navigating to Automator -> Status.

Since the report may contain sensitive information, feel free to send it to us privately at [email protected].

Fixes Included

To address these issues, I’ve included two updated files in this ZIP archive: Download the ZIP.

Please follow these steps to replace the files:

1. global.php:
   Replace the existing file at:
   wp-content/plugins/uncanny-automator/src/globals.php
2. trigger.php:
   Replace the existing file at:
   wp-content/plugins/uncanny-automator/src/core/services/rest/endpoint/log-endpoint/queries/view-queries/trigger.php

After replacing the files, please check if the issues are resolved and let us know.

If you encounter any further problems or need additional help, we’re here to assist you.

-S

Hi @whichtransfers , since it has been over a month since the last reply, we’ll go ahead and mark this ticket as closed.

Hi @dmorgan20 , since it has been over a month since the last update, we’ll go ahead and mark this ticket as closed. Please reach out though if we can help further.

Hi @kaklappen , since it has been over a month since the last update, we’ll mark this ticket as closed. Let us know though if we can help with anything else.

Hi @tonnyathylla ,

Since this ticket has been replied to from our Help Desk, we’ll close ahead and close it here.

Thanks

Hi @tonnyathylla ,

We did reply to the support tickets you logged, and hopefully that information was able to point you in the right direction. There is no known issue with Brevo on the Automator side, but you may need to authorize your site’s IP in Brevo settings and we do recommend copying a new Brevo API key into automator settings.

We are concerned about the review ratings, as this is a support question and the response we sent should help you get it resolved.

Please let us know though if we can be of more assistance.

Thanks

Hi @captainlin ,

Apologies for the delay.

Could you send us a screenshot of the recipe with everything expanded so we can see how the webhook request is set up?

The error message is coming from Discord and it suggests that you’re missing a parameter or have an empty token. If you are using tokens, we need to better understand how they’re being populated so we can figure out why what you’re sending might be blank or have missing data.

Thanks

Hi @adamverity ,

Apologies for the delay.

Right now what you want unfortunately isn’t possible. It will be in future and support is planned, but otherwise this would currently require some custom development.

Sorry about the bad news. I’ll tentatively close this ticket, as the request has been captured and a solution is planned (via a feature called “data loops” that will be available in an upcoming release).

Hi @adamverity ,

Try adding the index (/0/) to each customField, like this:

customFields/0/value
customFields/0/key

Here’s a screenshot that might help: https://share.cleanshot.com/HypjsBtj

Apologies for the late reply here.

Something like this would require our Pro plugin, which would give you access to the Schedule integration (see https://automatorplugin.com/knowledge-base/schedule/) to run actions repeatedly and user loops (see https://automatorplugin.com/knowledge-base/user-loops/) to loop through users and run the checks you need on them.

We hope that helps!

Sorry to hear about the issue.

Try navigating to Automator > Status > Tools, then use the icons on the right to purge the 4 views at the top. Once that’s done, click the Repair button to correct the views. This action won’t cause any data loss.

If there are still no logs after that, can you confirm if any other database issues are reported on that page? Are recipes still running as expected?

Thanks

Hi @chelminski ,

Thanks for passing on the details and alerting us to what’s happening.

Our team has prepared a fix, but since this is related to our Pro plugin, and this forum is for Uncanny Automator only, it’s not something we’re able to post here. We will plan to include it in the next release, and we’re happy to provide a copy if you’re able to reach out to our help desk from the account linked to your Pro license.

We will tentatively mark this as resolved since a fix is available.

Thanks again!

Hi @jdyach ,

As long as the order data you want is being stored by the plugin somewhere in the order details, then you can use post meta tokens (https://automatorplugin.com/knowledge-base/post-meta-tokens/) and pass in the ID of the order to retrieve that data. If the plugin uses custom tables, or you’re using Woo HPOS only (https://woocommerce.com/document/high-performance-order-storage/), then you would need to use our DB Query integration instead (or we can track this as a feature request to add an integration for your booking plugin).

As for user data, if this is our free version then it would be a logged in order trigger, in which case you can use a user meta token (https://automatorplugin.com/knowledge-base/user-meta-tokens/) to target the user’s phone number. You will need to know the meta key that’s used to store it though.

Product name is a token you should already see in the list of tokens for the trigger you’re using, though if you want one product per row in the Google Sheet, note that you would need to use a product-based trigger, like ”?A product?has its associated order?completed, paid for, or a thank you page visited”. This trigger does require our Pro plugin.

I hope that helps!

Hi @dmorgan20 ,

Sorry about the delay over the long weekend.

It would still really help to see the recipe details if possible; a screenshot with all details expanded would give us more context. We really need to see what action and tokens you’re using to help with troubleshooting.

If it’s any easier, I know you had a ticket open on our Help Desk more recently, and if you want to share screenshots and details there, that’s fine too.