Trigger on Query String Contains Program ID | Community
Skip to main content
Level 2
July 15, 2024
Solved

Trigger on Query String Contains Program ID

  • July 15, 2024
  • 2 replies
  • 2508 views

Is it possible to create a trigger for [Fills Out Form] with a [Querystring] constraint that if the query string contains {{program.id}}? Or do triggers have trouble activating based on fields and tokens? I tested this a few ways to Sunday with no activation of the trigger and I'm starting to think that {{program.id}} doesn't populate in time or at all for the trigger to activate but, I wanted to confirm if I've missed a process or solution to make this work as intended.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by SanfordWhiteman

{{program.id}} is an inherent property of the Program. It's always available, there's no race condition like what you're describing.

The cause is far broader: you can never compare field values with tokens in a Smart List. The only way to do what you're attempting here is with the assistance of a webhook-compatible service that can compare the values you send in the payload.

(Though if your goal is to associate a global form fillout with a program based on a query param, and you have such a service, you don't need to worry about the comparison. Just have the service add the person to the program with that ID.)

2 replies

SanfordWhiteman
SanfordWhitemanAccepted solution
Level 10
July 15, 2024

{{program.id}} is an inherent property of the Program. It's always available, there's no race condition like what you're describing.

The cause is far broader: you can never compare field values with tokens in a Smart List. The only way to do what you're attempting here is with the assistance of a webhook-compatible service that can compare the values you send in the payload.

(Though if your goal is to associate a global form fillout with a program based on a query param, and you have such a service, you don't need to worry about the comparison. Just have the service add the person to the program with that ID.)

Level 2
July 17, 2024

Ah, I see. Thanks for the insight as always. Sounds like we'll have to continue with just putting in the program ID by hand. Definitely not the end of the world.

Level 4
July 16, 2024

I would consider catching the Program ID querystring in your forms by creating a hidden string field that pulls from the URL parameter and using the data value change for that field as a trigger.

SanfordWhiteman
Level 10
July 16, 2024

That leaves you in basically the same boat, though. You need a condition for every possible program ID, just like if you use query string [contains].

Level 4
July 17, 2024

@sanfordwhiteman You're right. I was under the impression that the ask was for the trigger to fire on ANY form fillout with a Program ID attached to it. But the querystring makes much more sense for that scenario as well 😋