hybrid search action output variable usage in workflow
ART-1961_KNOWLEDGE_NODE-37
\n{{Ticket\xc2\xa0Created\xc2\xa0>\xc2\xa0Output\xc2\xa0>\xc2\xa0Reported\xc2\xa0By\xc2\xa0>\xc2\xa0Rev\xc2\xa0Org\xc2\xa0>\xc2\xa0Display\xc2\xa0Name}}.\xe2\x80\x9d\n\n\n\nDelay\n\n\n\nDuration: 2 minutes\n\n\n\nIf-else\n\n\n\nAttribute:\xc2\xa0Ticket\xc2\xa0Created/Output\xc2\xa0>\xc2\xa0Applies\xc2\xa0to\xc2\xa0part\xc2\xa0>\xc2\xa0Display\xc2\xa0ID  \nOperator: Equals  \nOperand: CAPL-18\n\n\n\nTicket  \ncreated\n\n\n\nEnd\n```\n\n[### Workflow action
Workflows | Computer by DevRev | DevRev
ART-1976_KNOWLEDGE_NODE-25
and effective resolution. Users can design workflows tailored to various scenarios; the example below illustrates a basic routing use case.\n\n| NODE | ACTIVITY |\n| --- | --- |\n| Trigger | Ticket created |\n| Action | Pick user by group |\n| Action | Update ticket |\n|  | ID: Ticket created > Output > ID |\n|  | Group > Output > ID |\n|  | Owned by > Set: Pick user > Output > User |\n\nOrgs can set up pull-based routing by updating the group instead of the user ID in the workflow illustrated
Routing | Computer for Support Teams | DevRev