Execute an email account intent
Create the intent’s mailbox at the email provider now and complete its task. Rarely needed: the mailbox is created on its own when the task is created without a date or wakes up on its date. Use it to retry after a refusal left the task PENDING with a comment. This is the only way to complete an EMAIL_ACCOUNT task: updateTaskStatus refuses it with TaskLockedByTypeError naming this operation. Safe to retry: an intent executed earlier answers outcome: ALREADY_EXECUTED and creates nothing again. Refused with TICKET_SCHEDULED before a scheduled task wakes up, TICKET_CLOSED, EXECUTION_IN_PROGRESS, EMAIL_ACCOUNT_ALREADY_EXISTS (the employee already has an account at an address other than their email), EMAIL_ACCOUNT_NOT_CREATED (the provider refused), COMPANY_SAAS_APPLICATION_NOT_CAPABLE; a refusal leaves the task PENDING with an internal comment on the ticket. For an onboarding still on the classic email step, the step is handled by the onboarding itself; this intent is the email work tracked as a task on a ticket (an EMAIL_ACCOUNT task), and never closes an onboarding email step.
Authorizations
Use your Primo API key in the Authorization header as Bearer <API_KEY>.