Kaseya Community

Home » Discussion Forums » Scripts & Agent Procedures » How to obtain AgentProcID

Learn more about how AuthAnvil can protect and enhance your Kaseya experience

Similar Posts

close of an alarm in dashboard

by
on Oct 19, 2015

set the IIS W3SVC1 log period (Command line or Agent Procedure)

by
on Nov 24, 2015

FAILED to load the THEN steps

by
on Jul 23, 2020
  • Verified Answer

Powershell - Execute PS1 script

by
on Apr 3, 2018
  • Not Answered

Create Script to Wait for User Response Before Executing Next Step

by
on Aug 16, 2012
Details
  • 4 Replies
  • 1 Subscriber
  • Posted1 month ago

How to obtain AgentProcID

  • m.dawson
    Posted by
    on Jan 23, 2021 10:28 AM

    Hi. I'm dabbling with automation using the REST API.

    To make calls I need the AgentProcID. This isn't something that is exposed in the VSA frontend (that i'm aware of). Thus far my database colleague has been getting it using some black art. 

    I was wondering if:
    A: there's a simple place where I can obtain the id?

    or

    B: Could i put some code in the procedure itself that could read it's own procid as a variable that I could capture and pass on to myself?

    Thanks in advance.

    Michael D
  • HardKnoX
    Posted by
    on Jan 23, 2021 1:58 PM

    Try exporting the Agent Procedure you want to run/schedule and open the XML file with a text editor, the Agent Procedure Id should be in there.
  • Paul Haaker
    Posted by
    on Jan 23, 2021 6:43 PM
    You should be able to use a SQL query to pull the ID from the ScripIdTab table.
  • m.dawson
    Posted by
    on Jan 29, 2021 10:21 AM

    Thanks for the ideas so far. Is there truly no way of automating the process of obtaining the procid? Surely there's a hack that can be used in the procedure itself to get it's own properties?
  • jondle
    Posted by
    on Jan 29, 2021 3:00 PM

    Wait...you're using the REST API and can't find the AgentProcedureId???

    You use the API for that. GET /automation/agentprocs

    Are you just not familiar with the ODATA style filtering?:

    GET /automation/agentprocs?$filter=AgentProcedureName eq 'PROC_NAME'

    Whether it is in something like Postman one time to hard code it somewhere or a more interactive interface. You're already setup to interact with the API and even the correct endpoint if you are scheduling.