Check an initial AppFolio API connection using verified provider-issued client settings. Read an approved test property listing and tenant records, then report only property IDs and a tenant count without creating or updating records.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Query AppFolio properties, units, and tenants via REST API. Trigger: "appfolio hello world".
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Get started with the AppFolio Property Manager API through a verified provider-issued client configuration. This skill walks through safe first reads for a property listing and a tenant count; create or update operations belong only in a separately approved synthetic sandbox workflow.
async function appfolioFetch(path: string) {
const res = await createVerifiedAppFolioClient().get(path);
if (res.status < 200 || res.status >= 300) throw new Error(`AppFolio ${res.status}`);
return res.data;
}
const properties = await appfolioFetch("/properties?page_size=10");
console.log(`Found ${properties.length} properties`);
properties.forEach((p: any) => console.log(` property ID: ${p.id}`));
const tenants = await appfolioFetch(`/tenants?property_id=${properties[0].id}`);
console.log(`Retrieved ${tenants.length} tenant records for the approved fixture`);
// Do not create a work order as a quickstart test. Continue only with the
// synthetic, idempotent workflow in appfolio-core-workflow-b.
A successful run proves the managed client and an approved safe-read endpoint work, returning only property IDs and a tenant-record count in its local output.
For a first integration check, configure the verified sandbox client, query one approved synthetic property page, and confirm its status, property IDs, and tenant count without recording addresses, names, unit numbers, or credentials. Do not create a work order merely to test access. If the portfolio contract, safe-read fixture, or response authorization is not verified, stop the run and use the credential owner’s staging process before attempting any mutation.
| Error | Cause | Solution |
|---|---|---|
401 Unauthorized | Invalid client_id or secret | Verify credentials in environment variables |
403 Forbidden | API scope not granted | Check Stack Partner permissions for the endpoint |
404 Not Found | Wrong base URL or endpoint | Confirm your company subdomain and API version |
422 Unprocessable | Missing required fields | Validate property_id and required body params |
429 Too Many Requests | Rate limit exceeded | Add backoff delay, batch requests |
See appfolio-core-workflow-a for full property and tenant management workflows.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Add a synthetic-data CI gate for customer-owned Abridge integration code. Test consent handling, note-review handoffs, redaction, and rollback behavior with mocked vendor boundaries, without connecting CI to a live Abridge or EHR tenant.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Triage Abridge recording, note review, Epic handoff, and access problems using observed symptoms and approved guidance. Identify the affected workflow stage, organize a minimal timeline, and prepare a redacted escalation record for the responsible team.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Map and review an Abridge clinical documentation workflow from consent and recording through draft review, evidence checks, edits, and final disposition. Keep clinician approval explicit, identify failure exits, and separate verified facts from tenant-specific details and pending approvals.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Audit how clinician-reviewed Abridge note sections map into Epic templates and downstream workflows. Use approved test records to document destinations, exceptions, evidence, rollback steps, and a go or no-go decision for a specific environment.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review Abridge adoption and workflow value using local usage records, clinician feedback, and verified contract costs. Build an evidence based decision table covering adoption, quality, support burden, and options to expand, hold, or improve the rollout.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Prepare a bounded support bundle for an Abridge issue using allowlisted operational details such as versions, coarse timestamps, and correlation references. Exclude recordings, transcripts, patient identifiers, credentials, and unrestricted logs, then document redactions and review details.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.