{ "id": "eHuvG2I1vOYj0U6k", "meta": { "instanceId": "1c7be698fdfa769249b0c65dcf8862b184efc981b9cec697fe71be1be502c151" }, "name": "My workflow", "tags": [ { "id": "isKwzRd30jBHOwft", "name": "AI", "createdAt": "2025-03-20T12:19:54.225Z", "updatedAt": "2025-03-20T12:19:54.225Z" }, { "id": "14BO5kV7hwR3aVmH", "name": "OAuth", "createdAt": "2025-03-20T12:19:58.622Z", "updatedAt": "2025-03-20T12:19:58.622Z" }, { "id": "hzAAB0A7DmXlEfor", "name": "Service", "createdAt": "2025-03-20T12:20:03.063Z", "updatedAt": "2025-03-20T12:20:03.063Z" } ], "nodes": [ { "id": "6503d6be-e4f3-4a06-b027-9fb210788a30", "name": "When Executed by Another Workflow", "type": "n8n-nodes-base.executeWorkflowTrigger", "position": [ 80, 340 ], "parameters": { "inputSource": "jsonExample", "jsonExample": "{\n \"name\" : \"Atlassian\",\n \"audience\" : \"api.atlassian.com\"\n}" }, "typeVersion": 1.1 }, { "id": "d6246380-096b-458f-a52c-b263c1e4b800", "name": "LLM Bus", "type": "@n8n/n8n-nodes-langchain.chainLlm", "position": [ 400, 340 ], "parameters": { "text": "You are an AI agent tasked with identifying the (pretty-print) OAuth service name, audience, authorization URI, and token URI.\nThe input is only a name bearing on the OAUth service, e.g.:\n1. Jira. The name Jira must be resolved to the correlated API service, in this case, Atlassian. OAuth information can be gleaned from https://developer.atlassian.com/.\n2. Sage. This is potentially a vague name. However, in the context of API and OAuth, it is probably Sage300 the ERP system. OAuth information can be gleaned from https://developer.sage.com.\n3. SAP. This can be the SAP HANA Cloud Platform. Authorization is usually be dedicated URL, e.g., https://:/sap/bc/sec/oauth2/client/grant/authorization?\n4. Google. This can be the Google API, e.g., https://accounts.google.com/o/oauth2/v2/auth? with audience as project-id-random-value.apps.googleusercontent.com.\n\nObtaining these details by just knowing the pretty-name of the service might be cumbersome. Therefore a confidence score, as a probabilistic indication your confidence\nof the data must be calculated. Express your confidence score on a scale of 1 (absolute certainty) down to almost zero (least certain), i.e., confidence NUMERIC(3, 2) CHECK (confidence >= 0.1 AND confidence <= 1.0).\nIf you can't obtain information, invent the data, but justify your improvisation by assigning a very low confidence score. You must always return a result, no matter\nhow low your confidence.\n\nThese Instructions comprise a Context Understanding, Information Retrieval, Output Format, an Example, with Accuracy and Verification. \n1. Context Understanding: The name (as input) value represents the target API or service. You need to identify the service name, audience, authorization URI, and token URI based on the name value. \n2. Information Retrieval: Use reputable sources and official documentation to find the correct service name, audience, authorization URI and token URI.\n3. Output Format: Service Name: [Service Name], [Audience], [Authorization URI], [Token URI], [Details]: (Your choice rationale in about 100 words to justify your answer), and lastly the [Confidence] (probability factor) as a numeric value 0 0 0