Neon CRM events

Neon CRM Events integrates Drupal with the Neon CRM API v2 so editors can pick a Neon CRM event from their account and sync its data into a Drupal node with a single click. Every event field — name, summary, description, dates and times, timezone, location, fee, registration URL, thumbnail, and publish/inactive status — is stored as a real Drupal field, so site builders can list and filter events using Views, build calendar feeds, or theme them however they like. Fields remain fully editable after syncing.

Features

• A new "Neon CRM Event" content type with 23 mapped fields, created automatically on install (no Field UI clicking required).
• A configuration page at /admin/config/services/neon-crm for your Neon Org ID, API key, and registration subdomain.
• An autocomplete picker on the node edit form that searches Neon for events by name.
• A "Sync from Neon" button that fetches the event over the API and populates every mapped field. The node is not saved automatically — editors review the values, edit anything they want, then save.
• A "Sync Title from Neon CRM" checkbox per-node so editors can keep a custom node title that survives future syncs.
• Full Views integration on every field — filter by date range, fee type, published/inactive status, and so on.
• A minimal Twig template that themers can override or replace; field labels and ordering are driven by the standard view display UI.
• HTTP Basic authentication and the NEON-API-VERSION: 2.11 header are handled internally; no extra modules required beyond Drupal core.

Additional Requirements

• Drupal 10 or 11
• A Neon CRM account with API access enabled and a system user with an API key

What this module is not

• It does not pull event registrations or attendee data into Drupal. The link out to Neon's hosted registration form is the entire registration flow.
• It does not download or store thumbnail images. The thumbnail URL is stored as a string and rendered as an <img src="…"> so it loads from Neon's CDN.
• It does not push data back to Neon. Sync is one-way (Neon → Drupal), on demand, per node.