Scrapybara icon

Scrapybara

Interact with the Scrapybara API
Join our community

Actions8

Overview

This node integrates with the Scrapybara API to manage and interact with virtual instances. Specifically, the "Resume" operation for the "Instance" resource allows users to resume a paused instance and optionally set a timeout duration before the instance is automatically terminated. This functionality is useful in scenarios where an instance was previously paused (e.g., to save resources) and needs to be restarted to continue processing or interaction.

Practical examples include:

  • Resuming a paused browser instance to continue automated web testing.
  • Restarting a paused Ubuntu or Windows instance to run additional commands or processes.
  • Managing cloud-based virtual machines that are temporarily halted to optimize costs.

Properties

Name Meaning
Instance ID The unique identifier of the instance to resume.
Timeout Hours Optional number of hours before the resumed instance is automatically terminated. Default is 1 hour.

Output

The output JSON object includes:

  • success: A boolean indicating whether the resume operation was successful.
  • instanceId: The ID of the instance that was resumed.

Example output JSON:

{
  "success": true,
  "instanceId": "your-instance-id"
}

No binary data is output by this operation.

Dependencies

  • Requires an active connection to the Scrapybara API via an API key credential.
  • The node depends on the external scrapybara client library to communicate with the API.
  • Proper API credentials must be configured in n8n to authenticate requests.

Troubleshooting

  • Common issues:

    • Invalid or missing Instance ID will cause the operation to fail.
    • Network or authentication errors with the Scrapybara API can prevent resuming the instance.
    • Attempting to resume an instance that is not in a paused state may result in an error.

  • Error messages:

    • "Failed to resume instance <ID>: <error message>" indicates the resume action failed due to API or instance state issues.

  • Resolution tips:

    • Verify the Instance ID is correct and the instance exists.
    • Ensure the API key credential is valid and has necessary permissions.
    • Confirm the instance is currently paused before attempting to resume.
    • Check network connectivity and API service status.

Links and References

Discussion