Skip to main content
  • EN

I’m looking to auto-create requestors, most likely using the WorkFlow Automator. We have all the information already within the Employee On-Boarding ticket. I feel it should be simple to go from the Employee On-Boarding to auto-create a new requestor. Maybe it’s already a built-in function that I’ve simply missed. Any assistance would be greatly appreciated.

 

Within my own attempts, I’ve tried doing the Web Request option. But I keep getting “Invalid Host”. Not sure what I’m doing wrong there but I don’t want to keep barking up that tree if it’s the wrong path for me go down.

Hi.

You could indeed automate the creation of them.

It seems you’re actually doing the right way.

Maybe, it is related to the actual URL you are using for the web call.

Please be advised that, if you have setup a Vanity/Custom URL, API web calls won’t work with it. You need to your the real FW instance name, instead of the Vanity/Custom (CNAME) URL.

You may want to check that.

 

Regards,

Hello there!

 

I’m very excited to announce that I was able to get a step further before receiving an error! Now when I test it or run the automation, I get a “405 Not Allowed” error. It’s not giving a lot more information for that. So if you have any ideas, please do tell! Otherwise, I’ll keep playing with it and see what I can do.

I’m looking to auto-create requestors, most likely using the WorkFlow Automator. We have all the information already within the Employee On-Boarding ticket. I feel it should be simple to go from the Employee On-Boarding to auto-create a new requestor. Maybe it’s already a built-in function that I’ve simply missed. Any assistance would be greatly appreciated.

 

Within my own attempts, I’ve tried doing the Web Request option Font Generator. But I keep getting “Invalid Host”. Not sure what I’m doing wrong there but I don’t want to keep barking up that tree if it’s the wrong path for me go down.

Yes, you can auto-create requestors using Workflow Automator. Since the data is already in the Employee On-Boarding ticket, set up an automation to trigger requestor creation upon ticket submission. If you're getting an "Invalid Host" error with Web Request, check your API URL, authentication, and request format. Also, verify if your platform has a built-in "Auto-create User" function to streamline the process.

I’m looking to auto-create requestors, most likely using the WorkFlow Automator. We have all the information already within the Employee On-Boarding ticket. I feel it should be simple to go from the Employee On-Boarding to auto-create a new requestor. Maybe it’s already a built-in function that I’ve simply missed. Any assistance would be greatly appreciated.

 

Within my own attempts, I’ve tried doing the Web Request option Font Generator. But I keep getting “Invalid Host”. Not sure what I’m doing wrong there but I don’t want to keep barking up that tree if it’s the wrong path for me go down.

Yes, you can auto-create requestors using Workflow Automator. Since the data is already in the Employee On-Boarding ticket, set up an automation to trigger requestor creation upon ticket submission. If you're getting an "Invalid Host" error with Web Request, check your API URL, authentication, and request format. Also, verify if your platform has a built-in "Auto-create User" function to streamline the process.

Hi ​@Kamakshi V . Not sure how or why an invalid/spam URL got in here. Would you mind removing / deleting all references to this Font Generator?

 

Regards,

Elvis

Ah, the joys of automation—where something that should be simple turns into a digital detective story! I’ve been exactly where you are, staring at that ‘Invalid Host’ error like it’s a riddle from the IT gods.

Here’s what finally cracked the case for me:

The Vanity URL Culprit

Turns out, Freshworks can be picky about web requests if you’re using a custom (vanity) URL. Instead of your nice, clean companyname.freshservice.com, you’ll need to use the original instance name—usually something like companyname123.freshservice.com. You can find this in your admin settings under Instance Info.

Workflow Automator Workaround

If the web request path feels like a dead end, try this:

  1. Set up a workflow that triggers when an onboarding ticket is closed.

  2. Use the Send Email action to shoot all the new hire details to your IT team (or yourself).

  3. Include a direct link to Create New Requestor in the email.

It’s not fully automated, but it cuts out 90% of the manual work while avoiding API headaches.

Pro Tip: If you’re logging how much time you’re sinking into this (I wasted half a Friday once), Calculadora de Horas is great for tracking whether automation is actually saving time—or just creating new puzzles!

Ever run into firewall issues with Freshworks? That was the next hurdle for us after fixing the URL!

Reply


Terms of Use