Integration
Connect Customer.guru to Non-Working Days
When something happens in Customer.guru, your agent does the next thing in Non-Working Days. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Customer.guru and Non-Working Days 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 Customer.guru and Non-Working Days
Triggers and actions 1 trigger · 7 actions
Trigger
New RatingTriggered when a customer submits a new rating on one of your Customer.guru surveys, giving you their score, their comment and how they engaged with the survey email.
Action
Find CustomerLooks up a customer in your Customer.guru account by email address and returns that customer's record — their id, when they were added, their most recent survey score and comment, and whether they have unsubscribed.
Action
Schedule SurveySends a Customer.guru NPS survey to one or more customers, either straight away or scheduled for a later date, and reports how many went out.
Action
Check leap yearCheck whether a given year is a leap year.
Action
Find date range statusesGet the working/non-working day status for every day in an arbitrary date range (up to 366 days).
Action
Get day statusCheck whether a given date is a working day, non-working day, shortened day, or holiday, with optional country, six-day-week, COVID and holiday-marking parameters.
Action
List month statusesGet the working/non-working day status for every day in a given month.
Action
List year statusesGet the working/non-working day status for every day in a given year.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.