Overview
The __circleci/0989fcb2-c8d2-43ed-bfdd-3ff63487e121 entry represents the system actor used when a custom webhook triggers a pipeline without identifying a registered CircleCI user.
This is not a hidden account or a user you need to invite. It is a fixed user identity used for custom webhook.
Why does this happen?
Custom webhooks authenticate with a webhook URL and secret. They do not authenticate with a CircleCI user token, so CircleCI does not receive a registered user profile for the request.
When no user profile is available, CircleCI uses the fixed user actor shown below. The entry can appear in Plan > Plan Usage > Users after the custom webhook trigger pipeline becomes active.
Does a custom webhook consume credits?
Yes. A custom webhook is not a free pipeline trigger. When it starts a pipeline, the resulting work consumes credits:
- Jobs that run consume compute credits.
- The actor can also consume user-seat credits, depending on the organization's plan and billing rules.
The webhook request itself does not have a separate per-request fee. If Prevent unregistered user spend is enabled, the pipeline may fail with block-unregistered-user instead of running work that consumes credits.
For details about compute and user-seat billing, see Using Credits.
Use the Trigger Pipeline API
If the pipeline must be attributed to a registered CircleCI user, use the Trigger Pipeline API with an authenticated CircleCI token instead of a custom webhook. Store the token securely and limit its permissions.
Registering the external webhook service itself does not convert the webhook into a registered CircleCI user.
Comments
Article is closed for comments.