acc_create_rfi
Create a new Request For Information (RFI) in an ACC project via the APS Construction RFIs API. RFI is created in 'draft' status — the project workflow owner typically transitions it to 'submitted'.
When to use: The user needs a formal question-of-record to the design or GC team — e.g. 'raise an RFI asking for clarification on the Level 2 beam schedule'. RFIs are the auditable channel for clarifications; issues are for field observations.
When NOT to use: Do not use for informal observations (use acc_create_issue) or to answer an existing RFI (not supported here).
APS scopes: data:read data:write account:read.
Rate limits: APS default ~50 req/min per endpoint per app. RFIs share the Construction API umbrella with issues (~100 req/min combined).
Errors: 401 (APS token expired — refresh); 403 (user lacks RFI create permission on project); 404 (project_id not found — verify 'b.' prefix and hub membership); 422 (validation — subject/question missing or priority enum invalid); 429 (rate limit — back off 60s); 5xx (ACC upstream — retry with jitter, check for duplicate before retrying).
Side effects: Creates a persistent RFI record. NOT idempotent — retry on 5xx risks duplicates; dedupe by subject before retrying.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| subject | Yes | Short RFI subject/title, 1–255 chars. Required. | |
| priority | No | RFI priority. Defaults to 'medium' if omitted. | |
| question | Yes | Full RFI question body. Plain text, up to ~10,000 chars. Required. | |
| project_id | Yes | ACC project ID. MUST use 'b.' prefix literal. Obtain via acc_list_projects. | |
| assigned_to | No | Optional APS user ID of the person the RFI is directed to. |