Post to Facebook

overview the post to facebook node publishes content from your workflow directly to facebook use it to automatically post text, images, or videos from your automation scenarios typical use cases auto posting updates when a new record is created in your database sharing daily kpis or reports as facebook posts posting marketing content created by other nodes (e g , ai text/image generation) announcing events, offers, or content uploads triggered from other systems node configuration 1\ authentication field authentication type facebook account / app connection connect your facebook account or page so simplita ai can publish on your behalf you must set this before the node can successfully post 2\ content type field content type type dropdown defines what you are posting text post – publish a post with text only (other content types like image/video may be available depending on your workspace configuration ) each content type determines which input fields are required (e g , text only vs text + media) 3\ state field state type dropdown controls when the post goes live publish immediately – post is published to facebook as soon as the node runs (if future options like “schedule” or “draft” appear, they will change how/when the post is created ) 4\ input field input type string (text) the main content of your facebook post you can type static text directly, or map data from previous nodes (for example, a message, summary, or generated caption) for media based content types, additional inputs (such as image or video urls) may appear and should be mapped from earlier nodes that produce or store those files 5\ result field result type json output the node returns a json object with metadata about the created post, such as post id post url timestamp use this output in later nodes (for logging, saving to a database, or sending confirmations) execution behavior when the scenario reaches this node, simplita ai uses the configured authentication to call the facebook api builds the post based on content type and input publishes according to state (e g , immediately) if the call is successful the node returns the result json with post details if there is an error (e g , invalid auth or missing required fields) the node fails and exposes the error details in the execution log, so you can debug and fix configuration issues best practices keep text clear and concise facebook truncates long posts in the feed template your text combine static text with dynamic variables from previous nodes (e g , {kpi value}, {date}) for more personalized posts log the result store the result json in a database or google sheet so you can track what was posted and when test in a sandbox/page first connect a test page while building your flow, then switch to production once you’re confident