This is a development reference. These bot features have not passed live checks
through the official bot’s app connection path. Keep them off in the first
four-feature pilot. A working app connection alone does not make them ready.
Before trying a connected feature
The server’s saved ApexGenius owner supplies the app connection. Check whose account that is and which project, list or calendar it may use. Discord staff access must not be treated as access to all of that account’s data. Ask the operator to verify the real tool list and one safe read first. A write also needs the proper app grant, tool access and any required approval. A team approval card is not a tool approval. Do not paste a personal app token into Discord to work around a failed connection. Scheduled reads can spend credits even when nobody presses a button. Check usage before starting a feed or board. Agree how long the test will run, then stop it. Do not promise a fixed cost until the official path has been checked.ClickUp tasks and boards
ClickUp tasks and boards
In the development build,
tasks supports ClickUp. Jira and Trello may appear
as choices but do not have working task adapters. Do not choose them expecting
task creation to work.An admin uses /task tool to choose the ClickUp list. Staff use /task tools
to see its setup and the bot’s read count. Start with a test list that holds no
private team work./task createtakes a required title and optional details in the command. Sending it queues task creation at once. Check the tool and target list with/task tools, then review your inputs before sending the command.- Apps → Create ClickUp task opens a form from a message. Check the destination, title and details before submitting that form.
/task findlooks up a task by name, ID or link in a private reply.- Change status and Comment on a task card change the task in ClickUp.
/task boardshows tasks in a forum. New task creates one. Ordinary messages in a post are not sent to ClickUp; use Comment or Apps → Send as task comment when that is intended./task digestmakes a summary of overdue work and the next seven days.
/task board stop:True and /task digest stop:True,
then turn the task tool off. Board posts remain. Remove test tasks in ClickUp
only when you own them and no one needs their history. Check both apps after
cleanup. No task-delete command is promised here.Feeds from GitHub, ClickUp, Forms and YouTube
Feeds from GitHub, ClickUp, Forms and YouTube
Turn on
feeds only for an agreed test. Admins choose a separate channel for
each feed. Use a private staff channel for anything drawn from private data.The first read records what is already there. New items are then posted, with a
limit per read to avoid flooding the channel. Existing GitHub cards update as
their source changes. A ClickUp feed follows only the tasks returned by its
read. Check large lists for missing tasks before relying on the feed.GitHub feeds are read-only. File, comment on and close issues in GitHub itself.
Forms Accept, Reject and Undo change the review card in Discord;
they do not edit the Google response. Keep Google access read-only.Use
/feed list to check the last read. A saved connection is not proof the
feed can read the chosen data. Fix access or usage limits before retrying.Stop and clean up: use /feed remove. Check that no new reads or posts
occur. Existing posts stay and may still hold app data; remove only the test
posts you no longer need. Stopping a feed does not revoke the app connection.Calendly bookings
Calendly bookings
The development path uses the saved owner’s Calendly account. Calendly remains
the source of truth for open times and booked meetings.Turn on
bookings only for an agreed test. Use /setup bookings-channel for a
private staff channel, then /booking panel for the member-facing card.
Members pick a time and enter the details Calendly needs. Meeting types that
need extra steps open Calendly instead.Use /booking status to see when bookings were last read. /booking sync
asks for a fresh read. Staff cards may take a few minutes to catch up with a
move or cancel. They can show a booker’s name, so check channel access first.Stop and clean up: cancel a test booking through Calendly’s confirmation
link or the Calendly app. The Discord bot has no move or cancel command. Check
the source booking and its Discord card, then turn bookings off. Remove the
member panel so people do not try to book through a stopped test.Salesforce Cases and alerts
Salesforce Cases and alerts
The development ticket build includes a Create Salesforce Case path. Its
official connected-app route is not ready for this pilot. Do not treat a test
Case as proof that the official bot can create one.Salesforce alerts and forum-to-Case work belong to a separate, parked release
scope. This guide does not enable them or tell you to deploy Salesforce metadata.If any test write has an unknown result, inspect the source app before trying
again. Agree the cleanup in advance. Do not retry a write just because Discord
did not show a success card.