Integration
Connect DevITjobs UK to Emailr
When something happens in DevITjobs UK, your agent does the next thing in Emailr. 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 Emailr 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 Emailr
Triggers and actions 1 trigger · 12 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
Add contactCreate a contact. POST /v1/contacts
Action
Add segmentCreate a contact segment. POST /v1/segments
Action
Add templateCreate an email template. POST /v1/templates
Action
Delete contactDelete a contact by ID. DELETE /v1/contacts/{id}
Action
Delete segmentDelete a segment by ID. DELETE /v1/segments/{id}
Action
Delete templateDelete a template by ID. DELETE /v1/templates/{id}
Action
Get contactFetch a contact by ID. GET /v1/contacts/{id}
Action
Get templateFetch a template by ID. GET /v1/templates/{id}
Action
List segmentsList contact segments. GET /v1/segments
Action
Update contactUpdate a contact by ID. PUT /v1/contacts/{id}
Action
Update segmentUpdate a segment by ID. PUT /v1/segments/{id}
Action
Update templateUpdate a template by ID. PUT /v1/templates/{id}
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.