I’ve also clicked “Allow Pipedream Support to access or edit this workflow”, so hope that helps 
I think that’s not normal. Could you also share your workflow URL? Maybe can do a check when he comes online.
@U05065WUZ1C could you share your workflow in Build mode by tapping the Edit button?
Fabulous, thanks 
Interestingly, in my other workflows that are working, the trigger isn’t visible in the deployments view either, so potentially not that issue.
I see. could you share your workflow url?
Thanks. Please wait for a few hours when comes online. He’s the one can check your case I think
Ok, perfect, thanks Leo, I’ll do some testing in the interim. See if adding a new form produce the same issue
Thanks again for all your help!!
I apologize for any inconvenience
No worries! I’ve managed to get the trigger working on a new form… can’t see any real difference between both setups other than it being a new form, very odd
All working with a new form now! Guessing there’s something wrong with the original workflow’s configuration, would be great to know why but not an urgent issue now
Thanks you for your time . I think we will still need to check it to be safe
Gothca, thanks Leo
Seems like the issue was resolved by creating a new Hubspot - New Form source?
yes , the issue is solved by creating a new source. Though I think the behavior Henry observed here in his workflow is weird
Henry, did you make a new workflow altogether to fix your issue? Is this original workflow still in the broken state?
I’ve made a new workflow and it seems to be all working now 
:skin-tone-2: All screenshots above are of the original, non-triggering, workflow.
So yes the original workflow is still in a broken state, this one here: https://pipedream.com/@moveai/create-channel-invite-from-discord-bot-api-p_G6CKO6d/inspect 