Skip to content

Shared components

These services are defined in org-runink/ui, not in PULSE. PULSE registers the shared Go handlers with its own hooks. For message fields, read the .proto files in that repository; this page covers what PULSE does with each service.

runink.ui.billing.v1.BillingService

The Billing page. See Billing.

MethodIn PULSE
ListPlans, QuotePlanWork. Pure price arithmetic over PULSE’s own plans, in US-dollar list prices.
GetOverviewThe viewer’s subscription (from their purchaser’s row in RUNINK_ACCOUNTS_FILE, else TENANT_ID and SUBSCRIPTION_*) and, on a trial, the seat’s daily fast-task count.
StartCheckout, OpenPortalNo payment provider: the answer is “not configured”, never an error and never a URL that leads nowhere.
ListSeats, AssignSeat, RevokeSeatPULSE keeps no seat roster.

runink.ui.datasources.v1.ConnectionsService

The Data sources tab. PULSE serves it over its own integrations table and narrows the catalog to HubSpot and GitHub.

MethodPurpose
ListConnectionTypesThe connector types offered: HubSpot and GitHub
ListConnections, ListConnectionNames, GetConnectionRead your connections
CreateConnection, UpdateConnection, DeleteConnectionManage them
RotateCredentialsReplace the stored token
TestConnectionCheck the token against the platform

A connection that sets a runner, an environment, or properties is refused, and nothing is stored.

runink.ui.datasources.v1.RunnersService

PULSE runs its connectors inside the server and has no remote runners. The service is registered so the shared page can say so. It reports no runners.

runink.ui.profile.v1.ProfileService

The Account page. Plan and usage are the billing section embedded in it.

MethodIn PULSE
GetProfileYour email, display name, and role from the users table, plus your session. Tenant from TENANT_ID (the platform keeps no tenant display name). PULSE has no platform admin, so the page does not show that row.
ListInstancesThe one instance this deployment serves, with your role and, when the instance’s member list states it, when your access ends (or that it does not). Without that list the expiry shows as not stated. Marked as a local development instance only when not running in a cluster. The app’s Admin menu entry reads this.
EndAllSessionsEnds all of your own sessions on every device

runink.ui.access.v1.AccessService

The Admin page. Admins only; the role is read fresh on every call. See Users and access.

MethodPurpose
ListMembersMembers and their roles
InviteMemberGrant a person a role. PULSE does not limit invites by seats.
SetMemberRoleChange a role. Not your own, and never the last admin.
RemoveMemberRemove a member. Not yourself, and never the last admin.

runink.ui.comms.v1.CommsService

Send and Call: WhatsApp, SMS and voice calls to a contact an admin has configured. Reads are open to any signed-in account, sending needs editor, and the contact list and carrier settings are admin-only. Carrier settings are sealed before they are stored.

MethodPurposeLeast role
GetCarrierStatusWhether messaging is configuredviewer
ListContactsThe configured contactsviewer
GetDelivery, ListDeliveriesWhat was sent and what became of itviewer
PrepareSendDraft and confirm a message before it leaveseditor
SendNotificationSend a WhatsApp message or SMS to a configured contacteditor
PlaceCallPlace a call to a configured contacteditor
UpsertContact, DeleteContactManage the contact listadmin
SetCarrierConfigSet the messaging carrier credentialsadmin

Delivery status arrives back on POST /comms/twilio/status; see HTTP endpoints.

runink.ui.chat.v1.ChatService

The assistant’s chat history (Settings › Chat history). The assistant starts empty on every page load, sign-in and app start; each question and answer is saved here instead, in PULSE’s own database, with the text sealed. Every method needs viewer and works only on the caller’s own chats: another person’s chat is NotFound.

MethodIn PULSE
ListChatsThe caller’s chats, newest first. An unreadable history is Unavailable, never an empty list.
GetChatOne chat and its messages, oldest first. A failed answer is kept and marked failed; a run or report it produced is its link.
CreateChatA new chat, titled after its first question. The subject is always assistant.
AppendMessagesAdds the question and the answer. A chat keeps its newest 400 messages.