Check credits when contact data fields change
A new contact field can be a cue to check the enrichment capacity behind your workflow.
Trigger
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Action
Get Credits
Get the current credit balance for the authenticated Datagma API account. Use this to check how many API credits remain before making enrichment calls.
Why this helps
Changing a contact schema can prompt a new round of enrichment work without anyone checking the available credit balance.
- Check capacity when contact enrichment needs change.
- Plan new lookups with current credit information.
- Avoid a separate account check after the schema work.
Setup
Build it in a few focused steps.
- 1Connect Notion and Datagma to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Tell Notis to check Datagma credits when a contact data source adds or changes an enrichment-related property, and report the balance.
- 4Choose the Notion Data Source Schema Updated trigger for the contact data source and a channel for run reports.
- 5Test with one real contact schema update and review the credit report.
Questions about this workflow
Can the trigger identify the changed field?
The event includes updated property IDs, names, and actions, so Notis can use those details to assess relevance.
Does this use Datagma credits?
The Get Credits action checks the current balance and does not perform enrichment.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Datagma. A trigger fires from one place; an action lands in another.
Notion triggers
Datagma actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Detect Job Change
Tool to detect if a contact changed jobs. Use when verifying a contact’s current employment details by email.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Enrich Person or Company
Enrich person or company data using LinkedIn URLs, emails, domains, or names. Returns enriched data including: contact information, LinkedIn profiles, company details, work experience, education, phone numbers (with phoneFull), and company metrics. Input types: LinkedIn profile URL (~100% success), email (~60% success), name+company (~90% success), company domain/name, or SIREN number (French companies).
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Find Work Email
Find verified work email address for a person using their name and company. Returns a professionally verified email address with validation metadata including SMTP checks and MX records. Requires either fullName or firstName+lastName, plus company domain or LinkedIn company slug.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
Get Credits
Get the current credit balance for the authenticated Datagma API account. Use this to check how many API credits remain before making enrichment calls.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Twitter Profile By Email
Retrieve Twitter account information associated with an email address. This action looks up Twitter username and display name for a given email address using Datagma's enrichment database. Returns Twitter username, display name, and the queried email if a match is found, or status 'NOT_FOUND' if no Twitter account is associated with the email. Use this when you need to: - Find someone's Twitter handle from their email address - Verify if an email has an associated Twitter account - Enrich contact data with social media information
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Get Twitter Profile by Username
Enrich Twitter profile data using Datagma's database. Returns contact information (email), social media profiles (LinkedIn, Facebook, GitHub), and professional details (skills, interests, industry) associated with a Twitter username. Note: Not all usernames are in Datagma's database. A 'not found' response (code 5) indicates the username hasn't been indexed yet.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Reverse Phone Lookup
Tool to reverse-lookup information associated with a phone number. Use when you have a phone number and need associated details (e.g., carrier, location).
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Search Phone Numbers
Find mobile phone numbers using email address and/or LinkedIn profile URL. Returns list of phone numbers with confidence scores and optional WhatsApp verification. Best results when both email and LinkedIn URL are provided.
Connect any two apps with Notis in the middle.
Notion and Datagma, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Datagma.