Integration
Connect Pumble to Non-Working Days
When something happens in Pumble, 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 Pumble 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 Pumble and Non-Working Days
Triggers and actions 1 trigger ยท 14 actions
Trigger
New MentionTriggers when a username is mentioned in a public channel.
Action
Create ChannelCreates a channel in the Workspace
Action
Find Channel by IDFind a channel by its ID.
Action
Find Channel by NameFind a channel by its Name.
Action
Find User by EmailFind a user by their Email.
Action
Find User by IDFind a user by their ID.
Action
Find User by NameFind user by their name.
Action
Send Channel MessageSend a message in a Pumble channel.
Action
Send Direct MessageSend a direct message to a user or yourself.
Action
Send Private Channel MessageSend a new message to a private channel or multi dm.
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.