Meta tags:
description=Build a first-notice-of-loss intake agent on a Nylas Agent Account — capture the claim email, pull photos and forms from attachments, file a per-claim folder, and route to an adjuster. Tagged with ai, email, api, productivity.;
keywords=ai, email, api, productivity, software, coding, development, engineering, inclusive, community;

Headings (most frequently used words):

the, claim, an, email, agent, what, you, mailbox, intake, insurance, claims, with, dev, community, actually, get, why, account, beats, shared, before, begin, receive, read, full, download, documents, file, per, folder, route, to, adjuster, acknowledge, claimant, guardrails, worth, knowing, next, ai, answer, pages, for, agents, top, comments, provision, fnol, more, from, qasim,

Text of the page (most frequently used words):
the (169), and (62), you (52), nylas (49), claim (33), #fullscreen (32), mode (32), your (27), for (27), email (26), with (24), message (24), that (22), agent (20), api (19), com (19), claims (19), grant (16), exit (16), enter (16), from (15), fnol (14), header (14), intake (13), account (12), dev (12), this (12), https (12), cli (12), attachment (12), same (12), one (12), body (12), post (11), mailbox (10), messages (10), content (10), 2026 (9), get (9), rule (9), what (9), not (9), attachments (9), grants (9), adjuster (9), webhook (9), folder (9), create (8), policy (8), are (8), inbox (8), before (8), inbound (8), workspace (8), curl (8), data (8), type (8), authorization (8), bearer (8), nylas_api_key (8), url (8), request (8), name (8), accounts (7), every (7), domain (7), clm (7), 0481 (7), message_id (7), call (7), read (7), app (7), folders (7), share (6), code (6), will (6), rules (6), reply (6), over (6), per (6), mail (6), into (6), application (6), json (6), download (6), created (6), open (5), new (5), through (5), shared (5), does (5), sender (5), based (5), routing (5), here (5), day (5), only (5), claimant (5), delete (5), endpoint (5), nylas_grant_id (5), auto (5), model (5), put (5), file (5), two (5), first (5), custom (5), yourcarrier (5), community (4), webhooks (4), threads (4), want (4), via (4), report (4), when (4), clean (4), know (4), full (4), once (4), limits (4), don (4), out (4), number (4), classification (4), can (4), its (4), photos (4), hands (4), metadata (4), need (4), signature (4), payload (4), grant_id (4), human (4), where (3), software (3), free (3), about (3), home (3), route (3), qasim (3), abuse (3), comments (3), but (3), top (3), workflow (3), agents (3), link (3), half (3), documents (3), right (3), registered (3), block (3), there (3), scoped (3), delivery (3), notification (3), dedup (3), evidence (3), line (3), reach (3), business (3), send (3), even (3), original (3), have (3), fetched (3), thread (3), sets (3), claimants (3), fetch (3), move (3), just (3), queue (3), everything (3), attach (3), which (3), both (3), whole (3), police (3), document (3), job (3), bumper (3), photo (3), attachment_id (3), each (3), value (3), key (3), description (3), against (3), own (3), thing (3), raw (3), secret (3), level (3), end (3), insurance (3), log (2), place (2), date (2), built (2), use (2), conduct (2), shop (2), database (2), organization (2), devtools (2), google (2), more (2), work (2), response (2), linkedin (2), hide (2), comment (2), answer (2), store (2), trusted (2), user (2), subscribe (2), industry (2), playbooks (2), answers (2), whether (2), ever (2), works (2), handoff (2), instead (2), gives (2), already (2), how (2), command (2), see (2), policies (2), overview (2), commands (2), fraud (2), domains (2), why (2), filed (2), lists (2), surface (2), supported (2), endpoints (2), next (2), because (2), least (2), means (2), record (2), acknowledgement (2), act (2), after (2), size (2), limit (2), dropped (2), spam (2), trash (2), pass (2), permanent (2), wipe (2), erasure (2), true (2), isn (2), things (2), flag (2), thanks (2), logged (2), within (2), field (2), populate (2), address (2), headers (2), subject (2), reply_to_message_id (2), close (2), loop (2), who (2), cannot (2), sees (2), desk (2), property (2), then (2), routes (2), sent (2), partner (2), until (2), update (2), array (2), add (2), drop (2), single (2), pdf (2), form (2), run (2), platform (2), jpg (2), show (2), under (2), object (2), separate (2), pull (2), loss (2), lives (2), reading (2), marking (2), unread (2), verify (2), any (2), compare (2), constant (2), guard (2), length (2), emails (2), event (2), across (2), all (2), twice (2), events (2), handler (2), hooks (2), standard (2), provider (2), connect (2), token (2), below (2), nothing (2), honest (2), has (2), owns (2), fire (2), front (2), oauth (2), copy (2), search (2), coders, stay, grow, their, careers, made, love, 2016, ruby, rails, powers, other, inclusive, communities, source, forem, terms, privacy, mlh, postgres, contact, showcase, advertise, help, education, tracks, videos, challenges, space, discuss, keep, development, manage, career, automate, appointment, reminders, calendar, notifications, pub, sub, gcp, shadow, test, live, testing, jun, joined, pronouns, toronto, ontario, canada, location, sre, swe, focused, observability, incident, reliability, scale, www, mqasimca, follow, further, actions, may, consider, blocking, person, reporting, confirm, child, well, sure, become, hidden, still, visible, permalink, dismiss, preview, submit, templates, let, quickly, faqs, snippets, template, personal, hub, topic, runbook, published, crawlers, retrieval, ready, version, pages, unglamorous, decides, glamorous, adjusters, digging, exactly, drive, above, plus, glance, warming, setup, provisioning, audit, trail, did, evaluations, including, pulling, conversation, history, idempotency, bug, duplicate, double, persist, fail, closed, count, allowed, mime, types, enforced, set, those, generously, lose, silently, stored, caps, driven, 200, storage, org, retention, high, volume, outgrow, tier, plan, moves, void, trashes, regulated, invokes, deleting, tell, compliance, plain, hard_delete, deletion, few, ship, guardrails, worth, knowing, required, preserves, fetches, recipient, automatically, references, example, moment, succeeds, instant, got, back, far, less, groups, acknowledge, developers, trip, impossible, llm, pattern, classify, saw, engine, says, flagged, always, goes, handles, server, side, match, operators, priority, remember, inert, ids, patch, workspaces, rule_ids, bodyshop, mark_as_read, assign_to_folder, in_list, contains, is_not, tld, now, levers, important, precise, claim_folder_id, moving, return, system, names, reserved, archive, junk, drafts, keeping, gets, lost, list, captured, bundle, working, directory, yours, was, intact, takes, positionally, writes, output, stream, bytes, disk, query, parameter, requires, part, makes, breaks, entry, everywhere, asks, watch, path, placeholder, comes, check, filename, committing, also, extraction, happens, happened, resulting, support, try, stash, itself, mapping, note, fetching, mark, false, state, prints, cleanly, signs, hex, hmac, sha256, using, time, buffers, equal, throws, mismatch, locally, crypto, timingsafeequal, treat, pointer, branch, exceeds, trigger, changes, omitted, regardless, inline, cross, constantly, truncated, trust, guarantees, retry, three, times, retries, inner, additionally, never, distinct, touch, afford, triggers, subscription, trigger_types, webhook_url, fires, arrive, carrying, filter, receive, creates, default, creation, stricter, tuning, later, say, tighter, cap, prototype, often, rather, than, lower, them, big, bundles, raise, carries, hold, onto, handle, follows, settings, optional, display, provision, skim, assumes, reference, sending, trial, subdomain, start, warm, roughly, four, weeks, stand, early, base, host, these, examples, authenticates, begin, off, microsoft, failure, modes, automations, expiry, way, give, identity, flips, integration, mental, spine, connected, auth, payloads, except, provisioned, yourself, authenticate, learn, plane, beats, known, bad, senders, shops, stays, being, scattered, dashcam, stills, reports, signed, forms, come, down, scraping, ocr, screenshot, nonsense, class, dedicated, outbound, acknowledgements, actually, terminal, exact, ones, wiring, step, ways, equivalent, either, stack, caveat, adjudication, deciding, pays, logic, getting, capture, real, sendable, receivable, shares, refresh, dance, hood, unchanged, receives, downloads, files, acknowledges, most, demos, point, triage, fine, realize, squatting, racing, inheriting, permission, headache, were, trying, escape, notice, heavy, sensitive, shows, dented, filled, land, bot, someone, shoulder, productivity, posted, jul, mastodon, facebook, copied, clipboard, boost, save, jump, raised, exploding, head, unicorn, like, reaction, powered, algolia, navigation, menu, skip,

Text of the page (random words):
e copy link copy link copied to clipboard share to x share to linkedin share to facebook share to mastodon share post via report abuse qasim posted on jul 4 intake insurance claims with an email agent ai email api productivity most ai for insurance demos point a model at a claims handler s mailbox and call it triage that s fine until you realize the agent is squatting in a human s inbox racing the human for unread mail and inheriting every oauth token and shared mailbox permission headache you were trying to escape first notice of loss fnol intake is document heavy and routing sensitive a single claim email shows up with photos of a dented bumper a pdf police report and a half filled claim form and all of it has to land in front of the right adjuster in one place with nothing dropped that s not a job for a bot reading over someone s shoulder it s a job for an inbox that is the agent that s what a nylas agent account gives you a real sendable receivable mailbox claims yourcarrier com that your code owns end to end no human shares it no oauth refresh dance under the hood it s just a grant with a grant_id so every endpoint you already know messages threads folders attachments works against it unchanged the agent receives the fnol downloads the evidence files a claim folder acknowledges the claimant and hands the whole thing to an adjuster i work on the nylas cli so the terminal commands below are the exact ones i reach for when i m wiring this up i ll show every step two ways the raw curl and the nylas equivalent so you can drop either into your stack one honest caveat up front this post is about intake capture and routing not claims adjudication deciding whether a claim pays out is your business logic and your model getting the claim its documents and a clean handoff to a human adjuster that s what the platform does for you what you actually get a dedicated fnol mailbox your code owns inbound claim emails fire the standard message created webhook outbound acknowledgements go through the same messages api as any grant attachments as first class data photos dashcam stills police reports and signed forms come down through the attachments api no scraping no ocr the screenshot nonsense per claim organization via folders so claim clm 2026 0481 has one home instead of being scattered across a shared inbox sender based routing through inbound rules block known bad senders auto file from partner body shops with the honest limit that content based claim type classification stays in your app why an agent account beats a shared mailbox if you ve ever run claims intake off a shared google or microsoft mailbox you know the failure modes two automations both marking the same mail read token expiry at 2 a m and no clean way to give your code its own identity the agent account flips that the mailbox is the integration the mental model is the spine of everything below nothing new to learn on the data plane if you ve built against a connected grant before this is the same v3 grants grant_id surface same auth header same payloads except you provisioned the grant yourself in one api call and there s no end user to re authenticate before you begin you ll need a nylas api key and a registered sending domain a custom domain or a nylas nylas email trial subdomain to start new domains warm over roughly four weeks so stand the mailbox up early the base host in these examples is https api us nylas com and every call authenticates with authorization bearer nylas_api_key new to agent accounts skim the agent accounts overview and the supported endpoints reference first this post assumes you know what a grant is provision the fnol mailbox create the account with a post v3 connect custom provider is nylas the email lives on your registered domain and an optional top level name sets the display name claimants see curl request post url https api us nylas com v3 connect custom header authorization bearer nylas_api_key header content type application json data provider nylas name claims intake settings email claims yourcarrier com enter fullscreen mode exit fullscreen mode the response carries a grant_id hold onto it it s the only handle you need for everything that follows the same thing from the cli nylas agent account create claims yourcarrier com name claims intake enter fullscreen mode exit fullscreen mode no workspace flag here the api auto creates a default workspace and policy on account creation if you want stricter limits or spam tuning later say a tighter attachment cap on a prototype agent you attach a custom policy to the workspace with nylas workspace update workspace id policy id policy id for fnol you ll often raise the inbound attachment limits rather than lower them claimants send big photo bundles receive the claim email inbound mail fires the standard message created webhook webhooks on nylas are application scoped not grant scoped you subscribe once at the app level with post v3 webhooks and events for every grant in the app arrive at that one endpoint each payload carrying the grant_id you filter on curl request post url https api us nylas com v3 webhooks header authorization bearer nylas_api_key header content type application json data trigger_types message created webhook_url https claims yourcarrier com hooks nylas description fnol intake enter fullscreen mode exit fullscreen mode or from the cli same subscription one command nylas webhook create url https claims yourcarrier com hooks nylas triggers message created description fnol intake enter fullscreen mode exit fullscreen mode two things to get right in the handler because claims intake cannot afford to act on a claim twice dedup on the notification id nylas guarantees at least once delivery and will retry the same event up to three times the top level notification id is constant across all retries of one event that s your delivery dedup key the inner data object id is the message id you can additionally guard on it so you never open the same claim twice even if two distinct events touch it don t trust the payload for the body treat the message created payload as a pointer not the document fetch the full message by id when you need the body and branch on message created truncated when a message exceeds 1 mb the trigger name changes and the body is omitted so you re fetch regardless fnol emails with inline photos cross that line constantly and verify the signature before you do any of it nylas signs each webhook with x nylas signature a hex hmac sha256 of the raw request body using your webhook secret compare it with a constant time compare but guard that both buffers are equal length first crypto timingsafeequal throws on a length mismatch locally the cli does it for you nylas webhook verify payload file raw body json signature x nylas signature header value secret your webhook secret enter fullscreen mode exit fullscreen mode read the full claim once the webhook hands you a message_id pull the whole thing body headers and the attachment metadata you ll need next curl request get url https api us nylas com v3 grants nylas_grant_id messages message_id header authorization bearer nylas_api_key enter fullscreen mode exit fullscreen mode from the cli nylas email read does the same and prints it cleanly nylas email read message id grant id enter fullscreen mode exit fullscreen mode this is also where your fnol extraction happens the claimant s name the policy number the loss date the description of what happened that s a model call against the body you just fetched and the resulting claim state lives in your own database agent accounts don t support custom metadata on messages so don t try to stash the claim number on the message itself own that mapping in your app one note on reading fetching with get does not mark the message read marking read is a separate put v3 grants id messages id with unread false if you want it download the claim documents this is the part of fnol that makes or breaks the workflow the message you fetched lists its attachments under an attachments array and each entry s id is the value you pass everywhere a download or metadata call asks for an attachment id watch this one the endpoint path placeholder is attachment_id but the value you put there comes from the attachment object s id field not a separate attachment_id key pull the metadata first if you want to check the filename and content type before committing to a download nylas email attachments show attachment id message id grant id enter fullscreen mode exit fullscreen mode then stream the bytes to disk over the api the download endpoint requires the message_id query parameter curl request get url https api us nylas com v3 grants nylas_grant_id attachments attachment_id download message_id message_id header authorization bearer nylas_api_key output claims clm 2026 0481 bumper photo jpg enter fullscreen mode exit fullscreen mode the cli takes the attachment id and message id positionally and writes the file for you with o nylas email attachments download attachment id message id grant id o claims clm 2026 0481 bumper photo jpg enter fullscreen mode exit fullscreen mode loop over the attachment list and you ve captured the whole evidence bundle photos the pdf claim form the police report into the claim s working directory from here it s yours store it run it through document ai attach it to the claim record the platform s job was to get it out of an email and into your hands intact file a per claim folder keeping every open claim in one inbox is how mail gets lost create a folder per claim so the fnol message and its thread have a single home an adjuster can open curl request post url https api us nylas com v3 grants nylas_grant_id folders header authorization bearer nylas_api_key header content type application json data name clm 2026 0481 enter fullscreen mode exit fullscreen mode nylas email folders create clm 2026 0481 grant id enter fullscreen mode exit fullscreen mode both return the new folder s id system folder names inbox sent drafts trash junk archive are reserved so name folders by claim number or adjuster queue route to the adjuster moving the message into the claim folder is a put that sets the message s folders array add the claim folder drop inbox and the fnol is filed curl request put url https api us nylas com v3 grants nylas_grant_id messages message_id header authorization bearer nylas_api_key header content type application json data folders claim_folder_id enter fullscreen mode exit fullscreen mode nylas email move message id folder claim folder id grant id enter fullscreen mode exit fullscreen mode now which adjuster you have two levers and it s important to be precise about which is which sender based routing is a rule if a partner body shop or a fraud flagged domain always goes to the same queue an inbound rule handles it server side before your app even sees the mail inbound rules match on from only from address from domain from tld with operators is is_not contains and in_list and can assign_to_folder block mark_as_read and so on so auto file everything from trusted bodyshop com into the priority queue is a clean rule remember a rule is inert until you attach it to a workspace via rule_ids patch v3 workspaces id or nylas workspace update rules ids claim type classification is not a rule here s the line developers trip over an inbound rule cannot read the subject or the body it only sees the sender so route auto claims to the auto desk and property claims to the property desk based on what the email says is impossible as a rule that s content classification and content classification is an llm call in your app code after the webhook the pattern is fetch the message classify it with your model then move it with the put messages id nylas email move you just saw the rule engine routes by who sent it your app routes by what it means acknowledge the claimant close the loop the moment intake succeeds claimants who get an instant we ve got your claim here s your number call back far less reply in thread so the acknowledgement groups with the original fnol curl request post url https api us nylas com v3 grants nylas_grant_id messages send header authorization bearer nylas_api_key header content type application json data reply_to_message_id message_id to email claimant example com body thanks your claim is logged as clm 2026 0481 an adjuster will reach out within one business day enter fullscreen mode exit fullscreen mode the to field is required on the send endpoint even for a reply populate it with the original sender s address you have it from the message you fetched the reply_to_message_id is what preserves the thread nylas sets the in reply to and references headers for you from the cli nylas email reply fetches the original to populate recipient and subject and threads automatically nylas email reply message id grant id body thanks your claim is logged as clm 2026 0481 an adjuster will reach out within one business day enter fullscreen mode exit fullscreen mode guardrails worth knowing a few things i d flag before you ship this deletion isn t erasure delete v3 grants id messages id moves mail to trash not into the void pass hard_delete true for a permanent wipe the cli s nylas email delete only trashes for a regulated workflow where a claimant invokes erasure the only true full wipe is deleting the grant delete v3 grants id nylas agent account delete don t tell compliance a plain delete is permanent it isn t free plan limits 200 messages per account per day 3 gb storage per org 30 day inbox and 7 day spam retention a high volume fnol line will outgrow the free tier size for it attachment caps are policy driven inbound attachment size count and allowed mime types are enforced by the workspace policy and over limit attachments are dropped from the stored message for claims set those limits generously or you ll lose evidence silently fail closed on dedup because delivery is at least once an idempotency bug here means a duplicate claim record or a double acknowledgement persist the notification id before you act not after what s next supported endpoints for agent accounts the full grant scoped surface including threads for pulling the conversation history before you reply policies rules and lists sender based routing block rules for fraud domains and the rule evaluations audit trail for why did this claim get filed there provisioning agent accounts domain warming and registered domain setup nylas cli commands every command above plus nylas agent overview to see your accounts policies and rules at a glance intake is the unglamorous half of claims that decides whether the glamorous half ever works get the email the documents and the handoff right and your adjusters open a clean claim instead of digging through a shared inbox the agent account gives you a mailbox that does exactly that and it s the same grant you already know how to drive ai answer pages for agents when this post...