Event types reference

What an event type is

When a trigger uses the On event kind, you choose one event type — the specific thing that must happen for the automation to run. This article is the full catalog of event types AppGram can fire, grouped by area, with the metadata each one carries.

Data every event carries

Whatever the type, an event exposes a common set of fields that steps and conditions read with ${event.…}:

• event.type — the event type slug, such as wish_created.
• event.title — a human-readable title for the thing the event is about.
• event.description — a longer description, when one applies.
• event.url — a link back to the entity in AppGram, when one applies.
• event.entity_id and event.entity_type — the ID and kind of the underlying record.
• event.project_id and event.organization_id — where the event originated.
• event.user_name — the person who caused the event, when known.
• event.timestamp — when it happened.
• event.metadata.… — type-specific fields, listed for each event below.

The metadata keys listed here are the ones AppGram guarantees for that event type, so they are safe to reference in conditions and step templates. When you pick an event type on the trigger, the builder lists its metadata fields in the config panel so you can insert them with a click.

Wishboard

• wish_created — a new feature request (wish) was created. Metadata: status, category_id, vote_count.
• wish_updated — a wish was edited. Metadata: status, category_id, vote_count.
• wish_status_changed — a wish moved to a different status. Metadata: old_status, new_status, category_id.
• wish_comment_added — a comment was posted on a wish. Metadata: comment_id, comment_author.
• wish_vote_added — a wish received a vote. Metadata: voter_id, vote_count.

Support

• support_ticket_created — a new support ticket was opened. Metadata: category_id, priority, requester_email.
• support_ticket_reply — a ticket received a reply. Metadata: ticket_id, author_type.
• support_ticket_closed — a ticket was resolved or closed. Metadata: ticket_id, resolution.

Status pages and monitoring

• status_incident_opened — an incident was opened on a status page. Metadata: severity, page_id, service_ids.
• status_incident_update — an incident received an update. Metadata: severity, page_id, update_status.
• status_resolved — an incident was resolved. Metadata: page_id, duration_minutes.
• monitor_alert_triggered — an uptime monitor entered an alert state. Metadata: monitor_id, monitor_type, endpoint.
• monitor_alert_resolved — a monitor alert cleared. Metadata: monitor_id, monitor_type, duration_minutes.

Billing

These events come from AppGram's own subscription billing for your organization.

• billing_subscription_created — a subscription started. Metadata: plan_id, amount, currency.
• billing_subscription_updated — a subscription changed plan. Metadata: plan_id, old_plan_id.
• billing_subscription_canceled — a subscription was cancelled. Metadata: plan_id, reason.
• billing_payment_succeeded — a payment went through. Metadata: amount, currency, invoice_id.
• billing_payment_failed — a payment failed. Metadata: amount, currency, reason.
• billing_trial_ending — a trial is about to end. Metadata: plan_id, days_remaining.

Forms and surveys

• contact_form_submission — a contact form was submitted. Metadata: form_id, submitter_email.
• survey_response — a respondent completed a survey. Metadata: survey_id, response_id.

Releases

• release_published — a release was published. Metadata: version, slug.

Competitor intelligence

These events fire from AppGram's Competitor Intelligence and are available only on plans that include that feature. Automations and templates that use them appear only for organizations with access.

• competitor_positioning_changed — a tracked competitor's positioning or capabilities shifted. Metadata: competitor_id, category, delta.
• competitor_sentiment_drop — sentiment for a tracked competitor dropped. Metadata: competitor_id, old_score, new_score.
• competitor_new_ads — a tracked competitor launched new ad creatives. Metadata: competitor_id, ad_count.
• competitor_mention_spike — mentions of a tracked competitor spiked. Metadata: competitor_id, channel, mention_count.
• competitor_digest_ready — a fresh competitor intelligence digest is ready. Metadata: digest_id, period.

A note on metadata

Extra metadata keys beyond the ones listed may appear on an event, but only the keys above are guaranteed. If a key is not present on a given event, a ${event.metadata.…} reference to it simply resolves to empty rather than erroring.

Next

Continue with Action steps reference for the full catalog of things an automation can do.