Keep a saved GIF easy to retrieve
If you rely on a particular GIF for a recurring moment, a page update can bring its details back into view without another hunt.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Get GIF by ID
Tool to fetch GIF metadata by its unique ID. Use when you have a valid GIF ID to retrieve metadata.
Why this helps
Useful visual references get lost among links, tabs, and forgotten searches.
- Retrieve metadata for a specific known GIF when needed.
- Keep a frequently reused visual associated with its Notion reference page.
- Skip a manual lookup when refreshing the reference.
Setup
Build it in a few focused steps.
- 1Connect Notion and Giphy to Notis once in the portal.
- 2Create an automation in the portal or ask Notis in a connected channel.
- 3In one instruction, tell Notis to retrieve the known Giphy GIF referenced by the page and return its metadata when the page content changes.
- 4Choose Page Content Updated for the reference page and select a channel for run reports.
- 5Test by updating the page containing a real Giphy ID.
Questions about this workflow
Does this search for a GIF if the page has no ID?
No. Get GIF by ID requires a valid known GIF ID. Keep the reference available in the page context and describe it in the instruction.
Does this display the animation itself?
The action fetches GIF metadata. How the result is displayed depends on the channel Notis uses for the run report.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Giphy. A trigger fires from one place; an action lands in another.
Notion triggers
Giphy actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Giphy Analytics Register
Tool to register user interactions (view, click, send) with a GIF for analytics. Use when you have the analytics payload, timestamp, and user ID to record the event.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Emoji Variations
Tool to fetch variations for a specific emoji. Use when you have an emoji's GIF ID and want its variations.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get GIF by ID
Tool to fetch GIF metadata by its unique ID. Use when you have a valid GIF ID to retrieve metadata.
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 GIFs by IDs
Tool to fetch metadata for multiple GIFs by their IDs. Use when you need information on up to 100 known GIF IDs.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Sticker by ID
Tool to fetch sticker metadata by its unique ID. Use when you have a valid sticker ID to retrieve metadata.
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 Stickers by IDs
Tool to fetch metadata for multiple stickers by their IDs. Use when you need information on up to 100 known sticker IDs.
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.
GIPHY Categories
Tool to fetch a list of GIF categories on GIPHY. Use when you need to browse available categories before selecting one.
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.
GIPHY: Get Category by ID
Tool to fetch metadata for a GIF category by its unique ID. Use when you need details for a specific category identifier.
Connect any two apps with Notis in the middle.
Notion and Giphy, 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 Giphy.