Integration
Connect DevITjobs UK to EOSL
When something happens in DevITjobs UK, your agent does the next thing in EOSL. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want DevITjobs UK and EOSL to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with DevITjobs UK and EOSL
Triggers and actions 1 trigger · 4 actions
Trigger
New job postingPolls https://devitjobs.uk/job_feed.xml (GET, no auth, no params) and fires for each new job listing appearing in the XML feed. Feed item fields: title, company, location, salary, description. No unique job id is published in the feed — implementer must derive a stable polling identity (e.g. hash of title+company+location, or publish date if present) since the vendor exposes only this one unauthenticated read endpoint.
Action
Find part statusLook up end-of-support/end-of-life status by part number in the lookup table. Endpoint: GET /data/lookup.json
- Get part status
Get a one-line end-of-support/end-of-life status for a single part number, suitable for spreadsheet lookups. Endpoint: GET /cell/{part}.txt
- Get product family
Get full end-of-support/end-of-life detail for one product family by its slug. Endpoint: GET /api/v1/family/{slug}.json
- List product families
List every tracked product family with its end-of-support/end-of-life status. Endpoint: GET /api/v1/families.json
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.