Get Page Insights: Facebook action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Page ID page_id	string	Required	Page ID. Example: 123456789
Metric metric	options	Required	Metric. Options: Page Impressions, Page Engaged Users, Page Post Engagements, Page Views Total, Page Fans (likes)
Period period	options	Optional	Period. Options: Day, Week, Month (28 days)

Sample request

{
  "page_id": "e.g. 123456789",
  "metric": "{{trigger.metric}}",
  "period": "{{trigger.period}}"
}

Returns

{
  "data": [
    {
      "name": "page_impressions",
      "period": "day",
      "values": [
        {
          "value": 1250,
          "end_time": "2025-01-15T08:00:00+0000"
        }
      ]
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Get Page Insights.

What does the Get Page Insights action do in Facebook?

Returns Page metrics — impressions, engaged users, post engagements, page follows, page views. Daily granularity. Useful for "weekly social performance digest" rollup workflows.

What inputs does Get Page Insights require?

Required: Page ID, Metric. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Facebook returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get Page Insights support batch operations?

Yes. Run Get Page Insights inside a Loop node to process arrays. Tiny Command handles Facebook's rate limits automatically so you don't have to throttle manually.

More actions