Hubspot as a trigger: when does the rule run?

English Forum Ask the Community
, , ,
1

Hi,

I love the fact that we cna now use Hubspot as a triogger to create tasks in Asana. However, I’m curious to know when the rule runs?

I created a rule with the trigger being If a record is created or updated, for when a specific property is changed to Yes, then it should create a task in a specific project and section, using the company name in the task name.

I am wondering how long I should wait until I see the task is Asana?

I updated a record in Hubspot on Friday for it to meet my trigger and I don’t see any task in Asana. Is it supposed to be instantaneous or am I missing something?

Thank you.

2

This is my rule.

Screenshot 2026-07-13 at 1.33.31 PM
Screenshot 2026-07-13 at 1.33.31 PM3312×1082 216 KB

3

Has anybody been able to successfully use HubSpot as a trigger?

I have done both: updating an existing record and creating a new one with the proper information for the right property to trigger the rule (in theory) but nothing happens.

The rule log only shows its creation. I am the rule owner, I created the project, I have access to all the properties needed in HubSpot used in the rule. I’m not sure what else to try?

The Asana’s chatbot keeps saying the same thing over and over again:

  1. Confirm the rule owner has current, real-time access to every item the rule touches (project, fields, etc.) and permission to create tasks. If access is missing, the rule won’t run.
  2. Re-test with a “backup” trigger that’s more reliable than “record updated” (for example, a trigger that fires when a specific field is set), since timing can cause the rule to evaluate before the update is fully applied.
  3. Keep “Runs on tasks and subtasks” as-is; it won’t prevent the rule from creating a task.
4

Hi @Virginie6

Could you try a more specific trigger than a broad “updated” event, and if the task already exists in the project, a manual rule trigger can help run it retroactively?

For example: if the task should be created when a HubSpot company property like “Send to Asana” changes to Yes, make that one change on a fresh record and save it. That’s a better test than a broad record updated event, because a generic update can include many different edits and may run before the final property value is fully available.

So in practice, I’d test this way:

  • Set Send to Asana = No
  • Save the record
  • Change it to Yes
  • Save again
5

Hi,

As you can see on the screenshot, I started with a specific property that needed to be updated to True.

When Company record is created or updated with Property Export Ready being True, then create a task.

I also tried with another company custom field.

I also tried with the trigger “when a record is created, create a task”. I tried with both Company and Contact.

6

Thanks! It looks like you’ve already tested the most common scenarios: a specific property changing to True, a generic record created trigger, and both Company and Contact records.

At this point, I wouldn’t keep waiting. These rules are expected to run when the trigger event occurs, and the conditions are met, so if the activity log still only shows the rule being created, it doesn’t appear to be a timing issue.

I’d first confirm that the rule is published and that the HubSpot connection for the rule owner is still active. If everything looks correct, I’d recommend reaching out to Support so they can review the integration logs and determine why the trigger isn’t firing.

7

Hi,

Thank you. All of these have been checked and I am currently in touch with Support via email.
I was curious to see if anybody had been able to make this integration work at all.