Import.io Schedules

Import.io scheduling — list, create and delete the run schedules of your extractors.

Type: Tool
Category: Data
Version: 1.0.0
Provider: InTouch AI
License: MIT

Provided free and as is, without warranty of any kind — including merchantability, fitness for a particular purpose, and the accuracy or completeness of any result. See the licence. You are responsible for checking what this produces before relying on it.

dataextractimportschedule

Import Schedule

Tool for the import-schedule API.

Base URL: https://schedule.import.io
Auth: query:_apikey (pass your key via the apiKey input)

Operations

get_extractor — GET /extractor — Get the list of schedules for all your extractors
get_extractor_extractorid — GET /extractor/{extractorId}/ — Get the schedule of a particular extractor
post_extractor — POST /extractor — Schedule and extractor to run at a specific time
delete_extractor_extractorid — DELETE /extractor/{extractorId}/ — Delete an existing schedule

Inputs

apiKey — your import-schedule API key
operation — one of the operations above
path parameters when an operation's path contains {...}
query — optional JSON object of query params
body — JSON object for create/update ops

Example

operation: get_extractor
apiKey: <your key>

Publishes

The keys a later task may reference as {{taskName.key}}. Referencing anything not listed here resolves to nothing at run time.

error
operation
result
status

Input Properties

Every property this tool accepts, from its own tool.iml.

Property	Type	Required	Default	Description
`apiKey`	string	yes	—	DEPRECATED — bind an API Key credential to the task with `credentialName` instead. A key pasted here is stored in the workflow definition in clear and appears in every export of it. Still honoured for workflows built before the change.
`operation`	string	yes	—	One of: get_extractor, get_extractor_extractorid, post_extractor, delete_extractor_extractorid
`extractorId`	string	no	—	Path parameter extractorId (required by some operations).
`body`	string	no	—	Request body as a JSON object string (for create/update operations).
`query`	string	no	—	Query-string parameters as a JSON object string, e.g. {"limit": 50}. Parsed and url-encoded onto the request.