Linked API icon

Linked API

Control your LinkedIn accounts and retrieve real-time data.

Actions27

Overview

The "Get Workflow Result" operation in the Linked API node is designed to retrieve the result of a previously executed workflow by querying its status and output. This is useful when you have triggered or run a workflow asynchronously (for example, via webhook) and want to programmatically check its completion status and fetch the resulting data.

Common scenarios include:

  • Polling for the completion of a long-running LinkedIn automation task.
  • Retrieving results from workflows that perform actions such as sending messages, fetching profile data, or managing connections.
  • Integrating with external systems where the workflow runs independently and the result needs to be fetched later.

Practical example:
You trigger a workflow that sends connection requests on LinkedIn. Instead of waiting synchronously, you use this operation to periodically check if the workflow has completed and then retrieve the success/failure details or any data produced.

Properties

Name Meaning
Webhook URL The URL where the workflow response will be sent via webhook. This is the endpoint that receives the asynchronous result notification.
Workflow ID The unique identifier of the workflow whose result you want to retrieve.
Workflow Operation The specific operation within the workflow to get the result for. Options include various LinkedIn-related actions such as: Check Connection Status, Comment on Post, Fetch Company, Fetch Person, React to Post, Remove Connection, Retrieve Connections, Retrieve Pending Requests, Retrieve Performance, Retrieve SSI, Search Companies, Search People, Send Connection Request, Send Message, Sync Conversation, Withdraw Connection Request, and their Sales Navigator equivalents.

Output

The node outputs JSON data representing the current status and result of the specified workflow operation. The structure typically includes:

  • Status information indicating whether the workflow execution is complete, pending, or failed.
  • Data payload containing the result of the workflow operation, such as retrieved LinkedIn profile details, confirmation of actions performed, or analytics data.
  • Metadata about the workflow execution like timestamps or identifiers.

If the workflow produces binary data, it would be included accordingly, but this operation primarily deals with JSON responses reflecting workflow results.

Dependencies

  • Requires an active API key credential for authenticating with the Linked API service.
  • Needs network access to the Linked API endpoint (https://api.linkedapi.io/automation).
  • The user must provide a valid webhook URL to receive asynchronous responses.
  • Proper configuration of the workflow ID and operation name to correctly query the desired workflow result.

Troubleshooting

  • Invalid Workflow ID: If the provided workflow ID does not exist or is incorrect, the node may return an error or empty result. Verify the workflow ID is correct.
  • Webhook URL Issues: If the webhook URL is unreachable or misconfigured, the workflow result might not be delivered properly. Ensure the webhook endpoint is accessible and correctly set up.
  • Operation Mismatch: Specifying an operation that does not correspond to the workflow's actual operation can cause errors or no data returned. Confirm the operation matches the executed workflow step.
  • Authentication Errors: Missing or invalid API credentials will prevent successful communication with the Linked API service.
  • Timeouts or Network Errors: Network connectivity issues can cause failures in retrieving workflow results. Check internet connection and firewall settings.

Links and References

Discussion